Wireless centrex call screen

ABSTRACT

The instant invention discloses a method and system for providing a novel wireless centrex service that untethers subscribers from the immobility associated with traditional desktop telephones. Essentially, the present invention extends the benefits of wireless voice and data services to subscribers having a need to move within a plurality of localities such as business and hospital campuses. 
     In accordance with the invention, a wireless telephone subscriber can use a standard cellular/PCS telephone as a wireless extension of their desktop phone, while in the proximity of a miniature radio base station capable of communicating with the PCS/cellular telephone. The advantage of such a system is that a subscriber can use the same cellular/PCS telephone that provides service in the public network in the wireless centrex environment. Additionally, the wireless centrex system provides services and features which are similar to those offered to regular centrex telephone subscribers. Exemplary features include, caller ID, call waiting, call hold, call transfer, call forwarding and voice messaging.

This application is a continuation-in-part of application Ser. Nos.09/224,272 filed Dec. 31, 1998 and 09/223,567 filed Dec. 31, 1998. Thisapplication relates to the provisional application serial No. 60/114,317filed Dec. 31, 1998. The complete disclosures of these applications arehereby incorporated by reference.

FIELD OF THE INVENTION

The instant invention relates generally to the field of communication,and more particularly, to the field of personal communications. Thepresent invention articulates methods and systems for extending thebenefits of wireless voice and data services to subscribers, especiallyin business premises and public environments, such as universities andhospitals. Furthermore, the present invention is geared towardsproviding methods and systems for processing and controllingcommunications in wireless communications and in a wireless centrexbased environment.

BACKGROUND

The challenges of an increasing mobile workforce have resulted inbusinesses migrating towards a more flexible and decentralized workingenvironment. These newly evolved environments have created a need forcommunication systems that must be capable of facilitating untetheredcommunication at any time and any place. Consequently, there is vastgrowth in emerging technologies that facilitate communication anywhereand anytime. Such technologies are employed in end user devices such aspagers, cellular telephones, and mail systems such as voice mail ande-mail systems.

There presently exists both wireline telephone network systems for homeand office use and cellular telephone systems for wireless mobile callsanywhere wireless services are offered (i.e., anywhere a user subscribedcellular base station reception can reach), which are interconnected toeach other through the Public Switched Telephone Network (PSTN). Assuch, a user has a choice of contacting other telephone users or beingcontacted by other telephone users by using either the wirelinetelephone system or the cellular phone system, each having their ownrespective detriments.

Wireline business telephone service is typically more economical thancellular phone service. However, if a user decides to use a wirelinetelephone as their only business telephone they can not be immediatelycontacted if they are not in their own office where their businesstelephone is physically located. Nor can the user easily make telephonecalls while not in his own office or on travel. On the other hand, if auser decides to have a cellular phone as their only business telephonethey can be contacted at anywhere at anytime but will likely incurhigher costs, e.g., airtime charges, which in total can be higher thanusing wireline telephone services. In the aggregate the cost of cellulartelephone service to all employees of a company is generally costprohibitive. In addition, a cellular telephone does not typicallyprovide the feature/function of a wireline telephone service (e.g.,Integrated Services Digital Network (ISDN) and centrexfeature/function).

Furthermore, if a user decides to have both a wireline telephone and acellular phone for their business use, they incur cost for using bothsystems and experience the inconvenience of having two separatetelephones and thus two separate voice mail systems to check formessages. A caller is also inconvenienced by having to call both theuser's wireline telephone number and the user's cellular telephone toreach the user.

Wireline telephone network systems (including ISDN and centrexcapabilities) and cellular telephone systems each have variousfeature/functions available to the user. Therefore, a need exists toprovide a wireless centrex system (WCS) having features and functionspresently available in existing wireline service and cellular services,as well as offering new feature/functions, while offering low costtelephone service for the working environment.

SUMMARY OF THE INVENTION

The instant invention addresses this need for an untetheredcommunication systems created by the paradigm shift towards a moreflexible and decentralized working environment. The material describedin the instant invention discloses a wireless communication platformthat provides a solution to the challenge of mobility management bymerging and expanding the capabilities of wired and wireless networks.Thus, the present invention includes systems and methods to provide awireless communication service that has expanded the features/functionsavailable in wireline and cellular telephone systems and the relativecost of the wireline system using a mobile telephone system and servicethat is added to existing wireline telephone systems equipment, to offercost effective wireless communications for the working environment.

The instant invention includes a wireless centrex system (WCS) thatallows a subscriber to use the same standard cellular/PCS telephone inboth the wireless centrex system domain as well as the public cellularsystem domain. In the WCS domain, subscribers can use their cellular/PCSas a cordless-like phone without incurring air-time charges. The WCS hasthe advantage of providing a working environment mobile telephone systemhaving traditional centrex and PBX type services such as call waiting,call hold, call forwarding, caller ID, three party conference calling,and call messaging. The WCS also includes additional enhanced featureslike message services used for paging, call screening, call waiting,distinctive ringing, user proactive call handling, automatic callback,call return and speed calling.

In general, the present invention is directed towards a method andsystem for extending the benefits of wireless voice and data systems toa wireless centrex system. The method and system as described in theinstant invention, provides flexible software driven support for futuregeneration air interfaces, as well as support for current legacy secondgeneration air interfaces.

In traditional centrex systems, subscriber's locations are fixed, and asa result, the call delivery mechanism to deliver a call to a subscriberis predetermined. However, in a wireless environment, the subscriber hasthe flexibility to continuously move throughout a specified coveragearea. Consequently, there exists a need to provide an intelligent calland message delivery mechanism. The instant invention introduces a novelcall delivery mechanism using an Advanced Intelligent Network (AIN) toachieve delivery. This AIN has a Service Switching Point (SSP) whichutilizes a triggering mechanism to determine the appropriate callhandling treatment for a specific call. As such, the system includes,for example, an existing local digital switch (LDS) as the SSP, anintelligent server (herein referred to as a network server platform(NSP)) coupled to the LDS for processing AIN communications, a pluralityof remote digital terminals (RDT) coupled to the LDS, a plurality ofintelligent transceivers (herein referred to as voice access ports(VAP)) coupled to the RDT (alternatively: the VAP could be coupleddirectly to the LDS), and a plurality of mobile stations (MS) whichcommunicate with the VAPs through an air interface (wireless).

Although a general WCS configuration with existing wireline centrexequipment has been provided as one preferred embodiment, there are manyother configurations possible some of which are shown (e.g., WCS usingPBX or having wireless data ports) and the basic system interfaces withother existing systems such as a PSTN and provider internet.

In operation, for example, the LDS upon receiving an incoming call witha directory number (DN) is triggered to communicate with a networkserver platform (NSP) to determine, using AIN, whether the DN has beenset up to be associated with a mobile station (MS) and WCS service. TheNSP tells the LDS to which of a plurality of VAPs connected to aparticular RDT the desired mobile station is presently registered with(connected to via air interface RF channel), and how to route the callto the mobile station having the mobile station identification number(MSIN) associated with the called DN. The various feature/functionsprovided in the WCS services of the present invention are summarizedbelow.

Feature Activation/Deactivation

Many of the feature/functions provided in the present invention WCSrequire selection by the mobile station user. As such, the presentinvention provides a system and method for a mobile station user toactivate and deactivate particular features/functions. For example, theMobile Station (MS) user dials a feature activation/deactivation codeinto a mobile station which is then sent to the intelligent transceiver(Voice Access Port (VAP)) over a digital control channel (DCCH) and theVAP sends an origination request message including the feature code toan intelligent server (network server platform (NSP)). The NSPdetermines whether the particular requested feature is authorized forthe particular mobile station requesting the feature and activates thefeature if it has been authorized. The NSP returns a message through theLocal Digital Switch (LDS) and the VAP to the MS indicating that thefeature is either activated or unavailable. If the feature/function codeentered into the MS is for deactivation the process is similar exceptthat the NSP checks to see if the feature/function is active and if so,turns the feature/function off. In this case, the NSP returns a messagethrough the Local Digital Switch (LDS) and the VAP to the MS indicatingthat the feature has been deactivated.

Call Hold

One feature of the present invention provides enhanced call holdfunctionality. The WCS service provides call hold/unhold functionalityfor a wireless commnunications unit (mobile station (MS)) so that a usercan place an active call or an incoming call on hold and retrieve thecall later. One aspect of the call hold feature of the present inventionallows a user to press a button, key, or key combination and/or buttoncombination on his mobile communications unit (MNS) to place an activeor incoming call on hold. Further, another aspect of the call holdfeature allows a user to press the same or a different button, key, keycombination and/or, button combination to retrieve the call from hold.The call hold feature may also allow the MS user to play a personalizedmessage to the party placed on hold.

A still further aspect of the call hold feature for the presentinvention allows a mobile phone subscriber to place an incoming call onhold without first having to answer the call. According to one suchembodiment, the calling party can be coupled to, for example, a voiceprocessing unit (VPU) to receive a message that indicates the call is onhold and the called party (WCS subscriber) will be with you shortly.Thus, the WCS of the present invention provides a user with the abilityto interactively place an incoming call on hold in real time withoutfirst answering the call, have the caller automatically instructed thatthe call is on hold, and to pickup the call sometime in the near future.

User Proactive Call Handling

Another feature of the present invention provides user proactive callhandle (UPCH) functionality and capability. This feature allows a mobiletelephone user to proactively handle a call in an intelligent wirelesscommunications system. A communications management methodology accordingto the present invention allows a user to proactively handle callsdestined to the user's terminal, e.g., a mobile station MS. One aspectof this feature allows a user to process and terminate an incoming callin real time.

According to an illustrative embodiment of the present invention, asubscriber is notified of an incoming call via a Short Message Service(SMS) message with caller ID or a user alert, such as a tone or ringing.Upon receipt of the alert, the subscriber may select from a series ofoptions, how to process and terminate the incoming call. For example, ifan incoming call is of high priority and requires immediate attention,the subscriber may decide to answer the call immediately. If thesubscriber decides that the call does not require immediate attention,he may opt to provide a delayed answer. Such a delayed answer option caninvolve connecting the call to an announcement prior to answering thecall. Still further, if neither of the prior options is suitable, thenthe subscriber may opt to send the call to a voice mail system, fromwhich a recorded message can later be retrieved. Yet another option ofterminating the call is to forward the call to another phone. In theevent that the subscriber decides that the incoming call should not beanswered, the subscriber may choose to reject the call. If thesubscriber decides that none of the aforementioned options should beproactively taken, then a default option can be used to terminate thecall. Such a default option may include, but is not limited to,forwarding the call, delaying the answer, sending the call to a voicemailbox, or rejecting the call.

Another aspect of the UPCH feature provides the ability to delayallocation of the voice channel to a called party until when, if at all,the incoming call to the called party requires a voice channel. This iscarried out by allowing a called party to receive notification of anincoming call over the control channel and to return the selection ofthe call handling options upstream over the control channel. Thus, avoice channel need not be allocated until the called party decides toanswer the call. This can be beneficial in wireless environments toprevent the unnecessary allocation of voice channels. Once the calledparty needs a voice channel, the incoming call has priority foravailable voice channels.

Call Transfers

Yet another feature of the present invention provides enhanced calltransfer functionality. The WCS services provides call transferfunctionality for a wireless communications unit (mobile station (MS))so that a user can transfer an active call to another DN, i.e., atransfer-to DN, that is within or outside the WCS. The MS user isprovided a quick, user friendly means to transfer an active call toanother DN. According to one variation of the call transferfeature/function the MS user enters digits for a call transfer featurecode and digits for the transfer-to DN, which are forwarded via a uniqueFeature Request message to an NSP to initiate the call transfer feature.After an NSP verifies that the MS is authorized to use the call transferfeature, a unique Transfer message is provided, an announcement isplayed indicating that call transfer is being initiated, and the activecall is placed on hold while a call setup is performed between the VAP(associated with the MS requesting a call transfer) and the transfer-toDN (which may be associated with either a PSTN or another MS).

In some situations the transfer-to DN may be busy or may not beanswered. In such cases, before the call to the transfer-to DN isanswered, the MS user can enter another key sequence (a button, key, orkey combination and/or button combination) to end the call transfer andretrieve the call on hold. On the other hand, when the call to thetransfer-to DN is answered a unique Transfer Result message is sent tothe NSP indicating that the call has been answered and the MS user canenter a key sequence which instructs the WCS to complete the calltransfer

Caller ID

Still another feature of the present invention provides enhanced calleridentification (caller ID) functionality. One feature of the presentinvention provides enhanced caller identification (Caller ID)functionality. The WCS service provides Caller ID functionality for awireless communications unit (mobile station (MS)) so that a user candetermine a caller's identity such as the calling party's directorynumber and location for an incoming or active call and decide how tohandle the incoming call, e.g., answer, not answer, forward to voicemail, etc. One aspect of the Caller ID feature of the present inventionallows display on the MS of the originating directory number (CallingParty Number) and identity for an incoming and/or active call, even ifthe call originates from another MS. Another aspect of the Caller IDfeature of the present invention provides the location and identity ofthe called MS 101 to the calling party and displayed on the callingparty's MS 101 during an active call. In either case, a Network ServerPlatform (NSP) provides the parties desk top phone directory number (DN)as their telephone number for Caller ID rather than the forwarddirectory number (FDN) associated with a voice access port (VAP) whichthe MS is presently associated.

A further aspect of the Caller ID feature provides that the callingparty may be initially coupled to, for example, a voice processing unit(VPU) including voice recognition capabilities, so that the callingparty can provide their name or other information which will bedisplayed on the MS of the called party. A still further aspect of theCaller ID feature allows display on the MS 101 of additional informationabout the calling or called party, for example their address, buildingnumber, company affiliation, etc. for an incoming or active call. The MS101 user can also disable the caller ID on a call-by-call basis. Thus,the WCS of the present invention provides a MS 101 user with the abilityto know the identity of the calling persons before answering a call andthe identity and location of a party they are speaking with on an activecall, even in the case when the calling party is calling from a WCS MS.

Screening Calls

An even further feature of the present invention provides call screeningfunctionality and capability. The WCS service provides call screenfunctionality for a wireless communications unit (mobile station (MS))so that a user can screen incoming calls to prevent the user from beingdisturbed by calls from parties with which the user does not wish tospeak. One feature of the call screen feature/function of the presentinvention allows a user to press a button, key, or key combinationand/or button combination on the MS to block out an incoming call(s)originating from a telephone number(s) specified by the user. The MSuser will specify a list of phone numbers (call screen list) for whichincoming calls are to be blocked when received. When any one of thephone numbers on the call screen list is the originating phone numberfor an incoming call directed to the MS, the system will block that callso that the MS user is not alerted and thus not disturbed.

A further feature of the call screen feature/function of the inventionenables an MS user to specify how the screened call(s) will be handled.The MS user can specify that the screened call may be, for example, sentto an answering service such as a voice mail system, provided anannouncement selected by the MS user, or dropped without anyannouncement.

Another feature of the call screen feature/function enables the MS userto enter a phone number to the screen call list of phone numbers byeither manually entering each digit of the phone number or by-indicatingthat the phone number of the last active call is to be added to the callscreen list. In the first case, the MS user can enter a phone number tothe call screen list by entering, for example, the call screen featurecode followed by the phone number to be blocked. In the second case, theMS user can dynamically enter a phone number in the call screen list byentering, for example, a particular key or entering the call screenfeature code without any phone number. The WCS will then determine thephone number of the last active phone call and add that phone number tothe call screen phone number list so that any incoming calls from thatphone number will be blocked.

Call Forwarding

Further aspects of the present invention provide a means for forwardingcalls to another number in a WCS 140 system. The number that the call isbeing forwarded to may be within or outside the WCS 140 system. Thereare several modes of call forwarding that are available. For example, acall may be unconditionally forwarded, forwarded after a certain numberof rings or upon the passage of a certain amount of time, forwarded inresponse to the called MS 101 being busy, and/or forwarded only duringone or more selected time periods. Moreover, one or more of these callforwarding modes may be used in any combination. For instance, a callmay be forwarded only during the weekend and only after a predeterminednumber of rings. The call forwarding feature(s) may beactivated/deactivated directly from the MS 101 to be called, fromanother MS, via a network such as a conventional telephone network orthe Internet, and/or by calling a Customer Care Center (CCC)representative.

Accordingly, an aspect of the present invention is directed to systemsand methods for forwarding an incoming call, the call originating from afirst communication device and being directed to a directory number of awireless centrex system. For example, the systems and methods maygenerate a message by a local digital switch in response to the call,and determine by a network server platform, responsive to receiving themessage, whether the call should be forwarded. The call may be eitherforwarded to the second communication device responsive to the networkserver platform determining that the call should be forwarded, or routedto a wireless mobile station having a forward directory numberassociated with the directory number responsive to the network serverplatform determining that the call should not be forwarded.

In a further aspect of the present invention, the systems and methodsmay determine by the local digital switch whether the wireless mobilestation is busy with another call. The call may be either forwarded bythe local digital switch to the second communication device responsiveto determining that the wireless mobile station is busy, or routed tothe wireless mobile station responsive to determining that the wirelessmobile station is not busy.

In yet a further aspect of the present invention, the systems andmethods may generate a current time and determine whether the currenttime is between a begin time and an end time. The call may either beforwarded to the second communication device responsive determining thatthe current time is between the begin time and the end time, or routedto the wireless mobile station responsive to determining that the callshould not be forwarded.

In a still further aspect of the present invention, the systems andmethods may alert the wireless mobile station and count a predeterminedamount of time in response to the call. The call may be forwarded to thesecond communication device responsive to the predetermined amount oftime being counted.

Call Waiting

The present invention also provides a method for call waiting in a WCSsystem. In particular, the call waiting functionality allows a user of amobile station (MS) to be notified of an incoming call when the MS isbeing used. That is, when an existing call between the MS user andanother party is ongoing, the MS user can be notified of another calldirected to the MS. The call waiting feature also allows the MS user toplace an ongoing call on hold and answer the incoming call. Further, theMS user may switch back and forth between the calls. Currently, there isno known call waiting service in a WCS system.

Distinctive Ringing

The present invention also provides a method for distinctive ringing ina WCS system. In particular, the distinctive ringing functionalityallows a user of a mobile station in a WCS system to receive adistinctive ring for a call originated from a communications unit havinga particular directory number (DN). A user can select one or more DNsfor which a distinctive ring will be received when a call is originatedfrom a unit assigned the selected DN.

Returning Calls

Still another feature of the present invention provides enhanced callreturn functionality. The present invention overcomes the drawbacksassociated with existing systems by providing a call returnfunctionality for wireless communication systems. The invention enablesautomatically placing the phone number of an incoming call, where thephone number is not unknown or security-protected, in a memory so thatthe call may be automatically dialed when it is convenient for theperson to return the call.

A user may wish to handle calls from different parties differently.Thus, in one embodiment, where more than one incoming call is received,the phone numbers for the incoming calls may be stored in a first-in,last-out viewing order on a display. Alternatively, the phone numbersfor the incoming calls may be stored in a first-in, first-out viewingorder or any predetermined order. In addition, prior to the wirelesscall return processor initiating dialing the phone number for theincoming call, the user may utilize the wireless call return processorto select which incoming call he wishes to return first by moving afirst displayed phone number to the end of a list of phone numbers ofincoming calls received and if desired, repeating this action.Alternatively, if the user desires to delay briefly returning the callassociated with the first displayed phone number call, the user maytranspose the first displayed phone number with a next phone number ofthe incoming calls received. Again, this action may be repeated asdesired.

Where the phone number is unknown or is security-protected so thatdisplay of the phone number is blocked, the display may indicate thatthe phone number for the incoming call is unable to be displayed.Alternatively, a voice prompt, a short message, or a predetermined tonemay indicate that the phone number for the incoming call is unknown orunable to be displayed.

Automatic Callback

Another feature of the present invention provides enhanced automaticcallback functionality. Present wireless handsets do not provide forautomatic callback to free the user from having to redial, perhapsrepeatedly, a number in order to complete a call. Clearly, there is aneed for a system, wireless apparatus and method for providing automaticcallback for a user in a wireless communication system when a callednumber is unavailable.

The present invention overcomes the drawbacks associated with existingsystems by providing an automatic callback functionality for wirelesscommunication systems. The invention provides for automaticallyredialing the phone number of a call when a number called by a wirelessuser is busy, thus permitting the wireless user to continue with otherwork and to answer the phone when the callback succeeds in connectingthe call.

When the call is connected, the wireless system may generate a voiceprompt via the wireless apparatus, a predetermined tone, an alert lightor the like, to notify the wireless user that the callback call isconnected. The wireless user may answer the call immediately, may pressa button or use a verbal command or commands to put a present call onhold and switch to the callback call. If the wireless user chooses toput the callback call on hold, a pre-recorded message from the wirelesssystem may be played for the callback caller to alert him that thewireless user will be answering his call in a very short time.

Speed Calling

The present invention also provides a method for speed calling in a WCSsystem. In particular, the speed calling functionality allows a user ofa mobile station in a WCS system to create a list of at least one phonenumber for which the subscriber utilizes a speed calling code to call atleast one phone number. A subscriber can then call a selected phonenumber by entering a provisioned speed calling code rather than a longertelephone number.

Conference Calls

Adding A Party To An Existing Call

Still another feature of the present invention provides enhancedconference call functionality. The WCS service provides conference callfunctionality for a wireless communications unit (mobile station (MS))so that a user can connect additional parties to an active call with aparty within or outside the WCS. The MS 101 user is provided a quick,user friendly means to add another party to an active call. Further, theMS 101 user is provided a quick, user friendly means to retrieve anoriginal call before a third party answers a call during a conferencecall setup.

According to one variation of the conference call feature/function, theMS 101 user enters digits for a conference call feature code and digitsfor the conference-with DN, which are forwarded via a Feature Requestmessage to an NSP 106 to initiate the conference call setup procedure.Once the NSP 106 verifies that the MS 101 user is authorized to use theconference call feature, a Feature Request Acknowledgement messagecontaining instructions to play a voice prompt to the MS 101 is providedto a VAP 103, an announcement is played indicating that a conferencecall is being initiated, and the active call is placed on hold while aconference call setup is performed between the VAP 103 (associated withthe MS 101 requesting a conference call) and the conference-with DN(associated with, for example, either a PSTN or another MS). After thethird party answers, the MS 101 user can press another key, for examplethe “send” button on the MS 101, to re-connect the original party(ies)to the conference call. However, if the WCS is unable to connect thethird party with the MS 101 user, the MS 101 user is prompted andnotified of the failure to connect allowing the MS 101 user to terminatethe conference call connection procedure by pressing another key, forexample the “send” button on the MS 101, to recover the previouslyactive call with the original party(ies).

In some situations the conference-with DN may be busy or may not beanswered, or the MS 101 user may simply decide they no longer wish toconnect the third party to the conference call. In such cases, beforethe call to the conference-to DN is answered, the MS user can decide toend the conference call connection procedure without prior system promptby entering another key sequence (a button, key, or key combinationand/or button combination) to end the conference call transferconnection procedure and retrieve the original call on hold. Forexample, the MS 101 user could press the “send” key twice within a shortperiod of time. In response, the conference call connection procedurewill cease, the call setup with the third party will be disconnected,and the original call will be retrieved.

Deleting A Party From An Existing Call

Still another feature of the present invention provides enhancedconference call functionality. The WCS provides conference callfunctionality for a wireless communications unit (mobile station (MS))so that a user can connect and disconnect parties to an active call witha party within or outside the WCS. The MS 101 user is provided a quickuser friendly means to delete a party from an active conference call.

According to one variation of deleting a party from a conference callfeature/function, the MS 101 user enters a party drop feature messageand the VAP 103 determines that the MS 101 user is requesting that thelast party added to a conference call be dropped. The VAP 103 will thenrequest the LDS 104 to drop the last added call of the currentconference call. The LDS 104 proceeds by sending the necessary messagesto have the last added call released from the conference call. Forexample, the MS 101 user could press the “send” key twice within a shortperiod of time. In response, the last added call to an active conferencecall connection procedure will be dropped by the LDS 104.

WCS As A Wireless PBX System

Another feature of the present invention includes a WCS which is aWireless PBX system. In this case, the system includes a IntelligentWireless Controller (IWC) that connects to a Customer Premises PBX andan NSP. The IWC and PBX will provide various functions performed by theLDS and RDT found in a typical WCS.

WCS With Wireless Voice And Data

Yet another feature of the present invention includes wireless datacapability with the WCS. In this case, laptop computers equipped with atransceiver interface with Data Access Ports (DAP) connected to anIntegrated Wireless Communication Controller to provide a wireless datasystem integrated with the WCS Voice Access Ports (VAP) and a LAN.

BRIEF DESCRIPTION OF THE DRAWINGS

For a more complete understanding of the present invention, reference isnow made to the following descriptions taken in conjunction with theaccompanying drawings in which like designations represent like parts,and in which:

FIGS. 1A-1C illustrates an exemplary wireless centrex system platformarchitecture.

FIG. 2 illustrates an exemplary wireless centrex network architecture.

FIG. 3 illustrates an exemplary signal flow diagram which demonstratesthe registration process which occurs when the mobile station is poweredon.

FIG. 4 illustrates an exemplary signal flow diagram which demonstratescall origination.

FIG. 5 illustrates an exemplary signal flow diagram which demonstratestermination of a call by a mobile station that answers the call.

FIG. 6 illustrates an exemplary signal flow diagram which demonstratestermination of a call by a mobile station that went unanswered.

FIG. 7 illustrates an exemplary signal flow diagram which demonstratescall termination to a roaming subscriber.

FIG. 8 illustrates an exemplary signal flow, diagram which demonstratesintra-local digital switch assisted handoff.

FIG. 9 illustrates a communications network for a wireless centrexsystem executed using a PBX system according an embodiment of thepresent invention.

FIG. 10 illustrates still another communications network for wirelesscentrex system capability having a wireless voice and wireless datawireless centrex system according to another embodiment of the presentinvention.

FIG. 11 illustrates an exemplary signal flow diagram which demonstratefeature activation/deactivation.

FIG. 12 shows a block diagram of illustrative communications networkaccording to yet another embodiment of the present invention.

FIG. 13 shows an exemplary signal flow for setting up an incoming callused for call hold/unhold feature, in accordance with an illustrativeembodiment of the present invention.

FIG. 14A shows a first exemplary call flow for the feature of callhold/unhold during an active call in accordance with an illustrativeembodiment of the present invention.

FIG. 14B shows a second exemplary call flow for the feature of callhold/unhold during an active call in accordance with anotherillustrative embodiment of the present invention.

FIG. 15 shows another exemplary signal flow for the feature of callhold/unhold of an unanswered incoming call in accordance with anillustrative embodiment of the present invention.

FIG. 16 shows an exemplary user proactive call handling signal flowdiagram for the activation and deactivation of the UPCH feature inaccordance with an illustrative embodiment of the present invention.

FIG. 17 shows an exemplary user proactive call handling signal flowdiagram for handling an incoming call when the UPCH feature is employedin accordance with an illustrative embodiment of the present invention.

FIG. 18 shows an exemplary proactive call handling signal flow diagramfor the delay answer call feature in accordance with an illustrativeembodiment of the present invention.

FIG. 19 shows a signal flow diagram for an exemplary call transfer to aPSTN telephone in accordance with an illustrative embodiment of thepresent invention.

FIG. 20 shows a signal flow diagram for an exemplary call transfer to amobile station in accordance with an illustrative embodiment of thepresent invention.

FIG. 21A illustrates a flowchart of an origination leg of a Caller IDinformation retrieval procedure for one preferred embodiment of thepresent invention.

FIG. 21B illustrates a flowchart of a termination leg of a Caller IDinformation retrieval procedure for one preferred embodiment of thepresent invention.

FIG. 21C illustrates a signal flow diagram for Caller ID informationduring call origination for one preferred embodiment of the presentinvention.

FIG. 21D illustrates a signal flow diagram for Caller ID informationduring call termination for one preferred embodiment of the presentinvention.

FIG. 21E illustrates a flowchart of an origination leg of a Caller IDinformation retrieval procedure for another preferred embodiment of thepresent invention.

FIG. 21F illustrates a flowchart of a termination leg of a Caller IDinformation retrieval procedure for another preferred embodiment of thepresent invention.

FIG. 21G illustrates a signal flow diagram for Caller ID informationduring call origination for another preferred embodiment of the presentinvention.

FIG. 21H illustrates a signal flow diagram for Caller ID informationduring call termination for another preferred embodiment of the presentinvention.

FIG. 22 shows a signal flow diagram for provisioning an exemplary callscreen in accordance with an illustrative embodiment of the presentinvention.

FIG. 23 shows a signal flow diagram for dropping a screened call withoutan announcement for an exemplary call screen in accordance with anillustrative embodiment of the present invention.

FIG. 24 shows a signal flow diagram for sending a screened call to avoice mail system for an exemplary call screen in accordance with anillustrative embodiment of the present invention.

FIG. 25 shows a signal flow diagram for dropping a screened call afterproviding an announcement for an exemplary call screen in accordancewith an illustrative embodiment of the present invention.

FIG. 26 is an exemplary flow chart of the unconditional call forwardingfeature of the present invention.

FIG. 27 is an exemplary signal flow diagram for signals generated when acall is successfully forwarded using the unconditional call forwardingfeature of the present invention.

FIG. 28 is an exemplary flow chart of the busy call forwarding featureof the present invention.

FIG. 29 is an exemplary signal flow diagram for signals generated when acall is successfully forwarded using the busy call forwarding feature ofthe present invention.

FIG. 30 is an exemplary flow chart of the time-of-day call forwardingfeature of the present invention.

FIG. 31 is an exemplary signal flow diagram for signals generated when acall is successfully forwarded using the time-of-day call forwardingfeature of the present invention.

FIG. 32 is an exemplary flow chart of the programmable ring callforwarding feature of the present invention.

FIG. 33 is an exemplary signal flow diagram for signals generated when acall is successfully forwarded using the programmable ring callforwarding feature of the present invention.

FIG. 34 illustrates an exemplary embodiment of an Internet web page foractivating and/or modifying features according to aspects of the presentinvention.

FIG. 35 shows an exemplary call flow diagram for the call waitingfunctionality according to an illustrative embodiment of the presentinvention.

FIG. 36 shows an illustrative flow diagram for the call waiting servicefeature according to an embodiment of the present invention.

FIG. 37 shows an exemplary call flow diagram for the actualimplementation of the distinctive ringing feature according to anillustrative embodiment of the present invention.

FIG. 38 is a signal flow chart showing signaling flow steps for anillustrative embodiment implementing a call return in accordance withthe present invention.

FIG. 39 illustrates one embodiment of steps for implementing a methodfor automatically returning an incoming call in a wireless communicationsystem in accordance with the present invention.

FIG. 40 is a block diagram of a wireless apparatus utilized forimplementing the method of the present invention in a wirelesscommunication system.

FIG. 41 is a flow chart showing another embodiment of steps inaccordance with the method of the present invention.

FIG. 42 is a block diagram of one embodiment of a wireless communicationplatform for providing automatic wireless call return in accordance withthe present invention.

FIG. 43 is a signal flow chart showing signaling flow steps for anillustrative embodiment implementing the automatic callbackfunctionality in accordance with the present invention.

FIG. 44 is a signal flow chart showing one embodiment of signaling flowwhen a mobile station MS moves from an original serving voice accessport VAPo to a new voice access port VAPn before a call is connected.

FIG. 45 is a flow chart showing one embodiment of steps of a method inaccordance with a preferred embodiment of the present invention.

FIG. 46 is a block diagram of a wireless apparatus utilized forimplementing the method of the present invention in a wirelesscommunication system.

FIGS. 47A-47C represent a flow chart showing another embodiment of stepsfor implementing the automatic callback feature of the present inventionwherein the wireless user is permitted to automatically re-dial the lastnumber dialed via a queuing process that sets up the call when thecalled line is idle. FIG. 47A illustrates steps during callestablishment/activation; FIG. 47B illustrates steps for one embodimentimplementing the NSP procedure. FIG. 47C illustrates steps for oneembodiment implementing the VAP procedure.

FIG. 48 is a flow chart showing another embodiment of steps inaccordance with the method of the present invention.

FIG. 49 is a block diagram of one embodiment of a wireless communicationplatform for providing wireless automatic callback in accordance withthe present invention.

FIG. 50 shows an exemplary call flow diagram for the actualimplementation of the speed calling feature according to an illustrativeembodiment of the present invention.

FIG. 51 is a first partial process flow diagram for a conference callprocedure in accordance with an illustrative embodiment of the presentinvention.

FIG. 52 is a second partial process flow diagram, related to the firstpartial diagram of FIG. 51, for a conference call procedure inaccordance with an illustrative embodiment of the present invention.

FIG. 53 shows a signal flow diagram for an exemplary three-wayconference call for adding a PSTN telephone to an existing PSTN—MS callin accordance with an illustrative embodiment of the present invention.

FIG. 54 shows a signal flow diagram for an exemplary three-wayconference call for retrieving an original call when a third party couldnot be connected to an existing PSTN—MS call for a conference call inaccordance with an illustrative embodiment of the present invention.

FIG. 55 shows a signal flow diagram for a three-way conference call forenabling an MS 101 user to initiate retrieval of an original call with aPSTN telephone of an existing PSTN—MS call without WCS prompting beforea conference call is established in accordance with an illustrativeembodiment of the present invention.

FIG. 56 shows a signal flow diagram for an exemplary deleting (dropping)of a last added party from an active conference call for a PSTNtelephone connection leaving an PSTN—MS two-way call, in accordance withan illustrative embodiment of the present invention.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

I. Acronyms and Short Hand Notations

Throughout the disclosure of the instant invention, several acronyms andshort hand notations are used to aid in the understanding of certainconcepts pertaining to the associated system and services. Theseacronyms and shorthand notations are intended solely for the purpose ofproviding an easy methodology of communicating the ideas expressedherein, and are in no way meant to limit the scope of the presentinvention. The following is a list of these acronyms:

AIN Advanced Intelligent Network ALS AT&T Local Services B-ChannelBearer Channel ATM Asynchronous Transfer Mode BER Bit Error Rate BRIBasic Rate Interface BS Base Station CB Communication Bus CSC CustomerService Center CLASS Custom Local Area Signaling Services DCCH DigitalControl Channel DAP Data Access Port D-Channel Data Channel DN DirectoryNumber DPU Directed Call Pickup with Barge-in DS1 Digital Service Level1 DS3 Digital Service Level 3 DSP Digital Signal Processor DTC DigitalTraffic Channel DTMF Dual Tone Multi-Frequency DVCC Digital VerificationColor Code EIA Electronic Industries Alliance FAC Feature ActivationCode FACCH Fast Associated Control Channel FDC Feature Deactivation CodeFDN Forward Directory Number GR 303 Generic Requirement 303 IDTIntegrated Digital Terminal/Switch IP Internet Protocol or IntelligentPeripheral IS-136 Interim Standard 136 ISDN Integrated Services DigitalNetwork ISP Internet Service Provider ISUP ISDN User Part ISUP IAM ISDNUser Part Initial Address Message ISUP ACM ISDN User Part AddressComplete Message ISUP ANM ISDN User Part Answer Message IWC IntelligentWireless Controller LAN Local Access Network LDS Local Digital SwitchMAHO Mobile Assisted Handoff MIN Mobile Identification Number MS MobileStation MSID Mobile Station Identification MSC Mobile Switching CenterNEL Next Event List NSP Network Server Platform OAM&P Operations,Administration, Maintenance, and Provisioning OC3 Optical Carrier Level3 OC12 Optical Carrier Level 12 PAD Packet Assembler/Disassembler PBXPrivate Branch Exchange PCH Paging Channel PCS Personal CommunicationsService POTS Plain Old Telephone Service PRI Primary Rate Interface PSIDPrivate System Identification PSTN Public Switched Telephone NetworkQ.931 Signaling Protocol Message Structure RDATA Relay data (Subfield ofIS-136 message) RDT Remote Digital Terminal RSSI Received SignalStrength Indicator SC Self Configuration SCP Service Control Point SMShort Message SMDPP Short Message Delivery Point = To Point SMS ShortMessage Service SMS Service Management System SMSCH Short MessageService Channel SNMP Signaling Network Management Protocol SONETSynchronous Optical Network SPACH SMS Point-to-point Messaging, Paging,and Access Channel SS7 Signaling System 7 SSP Service Switching PointSTP Signal Transfer Point STP Shielded Twisted Pair TAT TerminationAttempt Trigger TCP/IP Transmission Control Protocol/Internet ProtocolTCAP Transactional Capabilities Application Part TDMA Time DivisionMultiple Access TIA Telecommunications Industry Association UPCH UserProactive Call Handling VAP Voice Access Port VMS Voice Message SystemVPU Voice Processing Unit WCS Wireless Centrex System WCSD WirelessCentrex System Database X.25 Cross .25 (Data Packets)

Further, various telecom technical terms are used throughout thisdisclosure. A definition of such terms can be found in; H. Newton,Newton's Telecom Dictionary, 14^(th) Expanded Edition (1998). Thesedefinitions are intended for providing a clearer understanding of theideas disclosed herein and are in no way intended to limit the scope ofthe present invention and thus should be interpreted broadly andliberally to the extent allowed by the art and the ordinary meaning ofthe words.

II. General Overview of Wireless Centrex System Services

An illustrative methodology for implementing an intelligent wirelesscommunications system according to the present invention will now bedescribed below. While the systems and methods described below relate toa traditional cellular phone system or a wireless centrex system, it isto be understood that the present invention can be applied to all typesof wireless communications systems including, but not limited to,satellite systems, micro cellular systems, personal communicationsservices, and other mobile communication systems. Also, other types ofpersonal communications devices can be implemented in these systemsincluding, but not restricted to, a portable television, a wirelessvideophone, and a pager. Also, it is to be understood that the presentinvention can be applied to any type of wireless network, and that thedescription below is an illustrative embodiment for a system employingthe IS-136 EIA/TIA Interim Standard.

In one exemplary embodiment of the instant invention, the wirelesscentex system is deployed in an in-building environment with variouscommunication interfaces strategically located throughout the buildingto provide service within the building. In such an in-buildingenvironment, the mobile station (MS) assumes the characteristics of adesktop phone with all the Centrex capabilities being available to themobile user, plus the added advantage of mobility. A network ofpicocells served by Voice Access Ports (VAPs) are located within thebuilding and provides the cellular IS-136 air interface. The VAPs areintelligent base stations having ISDN BRI connectivity to a localdigital switch (e.g., Lucent 5ESS, Nortel DMS-100). FIGS. 1A, 1B, and 1Ceach show an exemplary VAP 103A connected to a Remote Digital Terminal(RDT) 102 via an ISDN BRI interface 2. Hereinafter, references to FIGS.1A through 1C will be referred to as FIG. 1, and have a common numberingscheme illustrating the various exemplary elements.

In fact, the same numbering will be used throughout the figures for likeelements. The Network Server Platform (NSP) 106 is an adjunct and can beco-located with a switch (LDS 104) to manage the VAPs and callprocessing control of the MS and provide the cellular (IS-136)operations for the VAPs. In one embodiment, when a call arrives for asubscriber to their POTS desktop phone 108 and it is not answered, theLDS 104 working in conjunction with the NSP 106 and the VAP 103A willforward the call to the subscriber's mobile station 101A over the VAP'sISDN B-channel 2 and the IS-136 air interface 3. The WCS system,therefore, offers the capability of a WCS subscriber being reachedanytime anywhere within the cell area of the WCS picocells. Further, ifa WCS subscriber also subscribes to a macro cellular system the callwill be handed off to the macro cellular system local Base Station (BS)when the subscriber leaves the WCS picocell areas.

The ISDN BRI lines 2 connecting the VAPs 103A and 103B to the switchcarry the signaling traffic on the D-channel (data channel) and thevoice traffic on the B-channel (bearer channel). The D-channel utilizesthe Q.931 protocol to establish a voice call on the B-channel with theLDS 104. The D-channel also carries signaling messages (X.25 packets)between the VAPs 103A and 103B and the NSP 106. An X.25 packetconnection is used to interconnect LDS 104 to NSP 106 and carry packetsrouted by the LDS 104 between the VAPs 103A and 103B and the NSP 106.The connection to the LDS 104 is not limited to a X.25 data packetconnection, but may be any connection supported by the LDS 104, andhaving an interworking function with the X.25 protocol. These packetscontain messages pertaining to call processing of the IS-136 interfaceas well as OA&M messages on the VAPs.

In one exemplary operation of the WCS, when a call arrives at thesubscriber's desktop phone 109, if the user does not answer, the switchwill use AIN triggers to request additional routing instructions fromthe NSP 106. The NSP 106 will locate the subscriber's MS 101 and directthe LDS 104 to forward the call to the VAP 103 servicing thesubscriber's MS 101. The NSP 106 will also inform the VAP 103 of theincoming call via messaging on the D-channel and direct the VAP 103 toestablish the IS-136 air link to the MS 101 in order to alert the user.When the user answers on their MS 101, the call is completed over theVAP's 103 ISDN B-channel and the IS-136 air interface.

In accordance with the principles of the invention, whenever asubscriber originates a call, the NSP will work in conjunction with theLDS 104 and the VAP to establish the RF link and the ISDN B-channelconnectivity to the switch. The switch will then route the call to theproper destination. When a subscriber moves from picocell (e.g., VAP103A service area) to picocell (e.g., VAP 103B service area), the NSP106 will inter-work with the switch and the VAPs and use the ISDNDirected Call Pickup with Barge-In to enable the seamless handoff. Forexample, when the MS 101A is on an active call served by VAP 103A, andis moving into the region served by VAP 103B, the NSP 106 will directVAP 103B to barge-in on the call on VAP 103A. This temporarilyestablishes a 3-way call and the NSP 106 will then direct VAP 103A todisconnect from the call, thereby leaving the active call to be servedby VAP 103B and completing the handoff. This is advantageous since theprocedure ensures that there is no noticeable interruption of the callon the network side.

In accordance with the principles of the instant invention, an exemplarynetwork platform architecture of a wireless centrex system (WCS) isillustrated in FIG. 1. The wireless centrex system disclosed therein,functions as a private wireless system which is not interconnected to apublic macro cellular system. However, the WCS system could also beinterconnected to a public macro cellular system. The wireless accessplatform provides a cordless-like, anywhere, anytime communications forindoor, business or campus-type environments. The key system elements ofthe WCS platform architecture are the Local Digital Switch (LDS) 104,the Remote Digital Terminal (RDT) 102, the Network Server Platform (NSP)106, and a wireless interface including one or more of a plurality ofVoice Access Ports (VAP) 103A and 103B and one or more of a plurality ofIS-136 Digital TDMA Cellular/PCS Mobile Stations 101A and 101B. AlthoughFIG. 1 illustrates the VAPs 103A and 103B being connected to the RDT102, the VAPs 103A and 103B may also be connected via ISDN BRI linesdirectly to the LDS 104, bypassing the RDT 102.

The WCS system of this embodiment may have, for example, the followingdesign attributes. There is one NSP 106 per LDS 104, although therecould be more than one LDS 104 per NSP 106. The NSPs, (e.g., NSP 106 andNSP 106A), are interconnected for inter-signaling using TCP/IP across anintranet, e.g., AT&T intranet 112. Centrex services and features areprovided via the LDSs, (e.g., LDS 104 and LDS 104A) and an SS7 network111. A single RDT 102 can provide interconnection of VAPs 103 for theWCS in a single large WCS office or multiple smaller offices as long asan ISDN BRI connection can be made to the VAPs 103. Further, the WCSsystem of this embodiment provides smooth handoffs between VAPs 103using the ISDN Direct Call Pickup with Barge-In (DPU) function. Finally,the WCS system can provide a secure wireless network by only recognizingpre-approved subscribers MS 101 for registration within the picocellarea covered by each of its VAPs 103; all other cellular phones withinthe picocell are prohibited from reception/transmission with the VAP's103.

The LDS 104 is a TR-08 and/or a GR-303 compatible LDS 104 which employsdistributed intelligence, process-oriented software, and coordinatedautonomous computing elements to provide a flexible, modular, reliableand robust digital switching system. LDS 104 has generic ISDN switchingfunctions with embedded AIN capabilities and provides networksynchronization. The Lucent 5ESS and the Nothem Telecom DMS-100 areexemplary Local Digital Switch (LDSs). The LDS 104 provides a singleplatform for advanced services including ISDN, Centrex, CLASS, CustomCalling, Advanced Intelligent Network (AIN), and basic bearer Channel (BChannel) call feature applications capabilities. It supports both X.25packet switched data communication and circuit switched data using, forexample, an X.25 Packet Assembler Disassembler (PAD) for signalingbetween NSP 106 and subtending VAPs (e.g., VAP 103A and VAP 103B). TheLDS 104 provides the switching fabric, administration, messageswitching, and call switching functions. The AIN capabilities on the LDS104 provides AIN software that enables the network provider to create,deploy, and change services to meet customers' requests. The AINsoftware allows the LDS 104 to act as an AIN Service Switching Point(SSP) to communicate with Service Control Points (SCP) (i.e. NSP 106 inthe WCS configuration), and Intelligent Peripherals. This gives the NSP106 the flexibility to manage call processing on the LDS 104. The eventswhich activate the AIN triggers must be provisioned so that they occurat specified points in a call where call processing may be interrupted,in order to interact with the NSP 106. Additionally, the LDS 104provides a gateway to a PSTN 125.

The Remote Digital Terminal (RDT 102) is a digital loop carrier terminalwhich supports POTS, ISDN, high-speed transport, and all specialservices—including private lines and PBX trunks. RDT 102 provides voice,data, and signaling transport and multiplexing of business premisetelephony equipment such as the ISDN phone 109, POTS phone 108, and VAPs103A and 103B. The Lucent SLC-2000 (pronounced “Slick” 2000) and theNortel Access Node are exemplary RDTs. The RDT 102 interfaces digitallywith the central office (CO), using, for example a TR-08 or GR-303 trunkconfiguration, connected with the LDS 104 such as a Lucent 5ESS or aNortel DMS-1000. The RDT 102 provides the distribution of serviceinterfaces between the LDS 104 and the customer premises, therebyextending the digital access network.

The exemplary NSP 106 provides control functionality for VAP 103A and103B, which includes mobile station and mobility management, callcontrol such as handoff, wired and wireless interworking such as DN andMIN mapping, signaling processing interface and management, AIN for callprocessing, service creation and management and feature applications,along with related OAM&P functions. The NSP 106 is also responsible forNetwork Intelligence and resource management including RF management(e.g., SC), validation or authentication, registration, and MessageCenter operation and control.

An illustrative NSP is described in co-pending U.S. patent applicationSer. No. 09/100,360 entitled “Hybrid Fiber Twisted Pair Local LoopNetwork Service Architecture” by Gerszberg et al., which is hereinincorporated by reference. While the NSP described by Gerszberg et al.is not for a wireless centrex system, it can be modified to work in theWCS of the present invention. In the WCS environment, the NSP 106 mayinclude NSP specific software operating on a high performance, generalpurpose computer, for example, a SUN SPARC Enterprise server E3500.

The exemplary Voice Access Ports (VAPs) 103A and 103B are pico-cellularintelligent base stations or radio transceiver ports that support, forexample, the IS-136 air interface with IS-136 mobile stations such asdigital TDMA cellular/PCS communications units 101 a, 101 b. IS-136 isthe EIA/TIA Interim Standard that addresses digital cellular and PCS(personal communications services) systems employing time divisionmultiple access (TDMA). IS-136 specifies a DCCH (Digital ControlChannel) to support new features controlled by a signaling and controlchannel between a cell site (e.g., radio base station) and terminalequipment (e.g., mobile station). The IS-136 air interface between theVAPs 103 a, 103 b and mobile stations MS 101 a, MS 101 b can supportvoice and messaging applications. The mobile stations MS 101 a, MS 101b, etc., may be, but are not limited to, a terminal or a typicalcellular/mobile phone having a keypad, display screen, and an alarmgenerator for generating a ringing or tone sound.

The VAPs support plug-and-play operations by connecting to RDT 102 viastandard open interfaces, such as ISDN BRI. In one embodiment, the VAPs103A and 103B use advanced digital software radio technology forsuperior RF performance. Additionally, VAPs 103A and 103B may employself configuration algorithms for “stacked spectrum” operations. U.S.Pat. Nos. 5,809,423, 5,787,352, 5,740,536, 5,404,574, and 5,345,499describe exemplary algorithms and related methodologies that may beutilized in self configuration for “stacked spectrum” applications. TheVAPs also administer resource management.

The mobile stations (MS) 101A and 101B provide the WCS subscriber withcordless-like services feature/function, thereby permitting usermobility within the WCS service coverage area. The IS-136 digital TDMAcellular/PCS mobile stations 101A and 101B, may include, for example theNokia 2160 and the Ericsson DH368 TDMA digital telephones. Onesignificant advantage of the instant invention is that a base stationmay be interconnected to a switch via an open standard interface, suchas ISDN BRI, so that traditional wireline services, such as centrex typeservices features/functions like call hold, call forward, call waiting,call transfer, speed calling, caller ID, three party (conference)calling, etc., may be offered to MS 101.

In one exemplary embodiment of the WCS, there are five major interfacesas illustrated in FIG. 1. With reference to FIG. 1, interface 1,connects the LDS 104 to the RDT 102 using, for example, the Bellcorestandard GR303 interface. The GR303 standard defines digitaltransmission facility interfaces such as DS1 and SONET, concentrationoptions between the integrated digital terminal/switch (IDT) 105 and theRDT 102, signaling options, and call processing and operations datalinks. The transport media for this interface can be, for example,metallic or fiber-optic. Exemplary metallic media include T1, ISDN/PRIand DS3, while exemplary fiber-optic media include SONET OC3 and OC12links. Interface 1 carries the voice traffic of a telephone call, aswell as the signaling traffic for the LDS 104 and the NSP 106.

Interface 2, connects the VAPs 103A and 103B to the RDT 102 with, forexample, ISDN/BRI lines (2B+D channels), using the Q.931 signalingprotocol on the D-channel to setup the voice connection on theB-channel. In this case, the RDT acts only as a transport for thesignaling and data message to the LDS 104. WCS call processing messagesfor call setup, call teardown, feature applications on the RF (IS-136)and OAM&P messages are carried over X.25 packet, interface 4, on theD-channel between the NSP 106 and the VAPs 103A and 103B, via the LDS104 and the RDT 102. These messages are sent to the LDS 104, whichroutes them to the NSP 106. Voice connections between the VAPs 103A and103B and the LDS 104 are carried on the B-channel via the RDT 102.Additionally, software downloads from the NSP 106 are also carried onthe D-channel or B-channel to the VAPs 103A and 103B via the LDS 104 andthe RDT 102. In one exemplary embodiment, the RDT 102 acts as aconcentrator and its operation is transparent to the operation the WCS.

Interface 3, may be, for example, an IS-136 air interface between theVAPs 103A and 103B and the MSs 101A and 101B supporting voice andmessaging applications. Interface 4 is, for example, an X.25 protocollink between the NSP 106 and the LDS 104. Call control and OAM&Pmessages between the NSP 106 and the VAPs 103A and 103 b are carried onthe D-channel of interface 2 through interface 1, through the LDS 104,and over this X.25 link.

Interface 5 may be, for example, an SS7 link connecting the NSP 106 andthe LDS 104. This exemplary interface carries AIN messages which aregenerated by the LDS 104, sent to the NSP 106 for processing, and sentback to the LDS 104 to instruct the LDS 104 how to route the callproperly. Interface 5 carries AIN messages from the LDS 104 which notifythe NSP 106 of AIN trigger events. It also carries responses from theNSP 106 to the LDS 104 which instructs the LDS 104 how to properly routecalls to the WCS subscribers.

When the IS-136 cellular/PCS mobile stations 101A and 101B are locatedwithin the WCS system coverage area, MIN-based calls to the publiccellular network destined for mobile stations 101A and 101B may not bedelivered in the WCS service area. Instead, the IS-136 phones can beassociated with the DN of a stationary phone (e.g., POTS 108 or ISDN109) within the WCS services area so that the LDS 104 delivers the callto either the subscriber's MS 101 or the subscriber's stationary phoneusing the DN. On the other hand, when the subscriber's mobile station MS101 is located outside the WCS service area, calls are delivered to themobile stations through the MIN provided in the public cellular system.

After a simple registration process, the WCS subscribers use theirIS-136 digital TDMA cellular/PCS phone 101A or 101B as a cordless-liketelephone within the wireless centrex service area without incurringair-time charges. Typically, when an incoming call destined for a WCSsubscriber's DN reaches the LDS 104, and the DN was previouslyprovisioned for AIN treatment, an AIN trigger occurs in the LDS and anAIN query message is sent to the NSP 106. In one embodiment, each WCSsubscriber has a reachable desktop DN and each DN will be programmed forthe AIN trigger in the LDS 104 for call routing purposes. The NSP 106provides appropriate routing instructions to the LDS 104 for delivery ofthe incoming call. The NSP 106 can locate and alert the subscriber'smobile station and direct the LDS 104 to route the incoming call to themobile station (MS 101). If the subscriber does not answer, the NSP 106may direct the LDS 104 to route the incoming call to a Voice MessageSystem (VMS) 107, which ultimately answers the call. An exemplary VMS isthe Lucent Conversant Model MAP/100C (MultiAccess Platform). Callsinitiated from a stationary phone such as POTS 108 or ISDN 109, ormobile station 101 within the WCS service area are sent to the LDS 104that can handle the call or route the call to the PSTN 125.

The WCS is a self-configurable indoor wireless system that applies the“stacked spectrum” concept. It can detect (sniff) and designate unusedand interference-free DTC/DCCH (Digital Traffic Channel/Digital ControlChannel) from the overlayed (e.g., macro or micro) cellular system, forits own use, based on the unique WCS private systems number (PSID). TheDTC is defined in IS-136 as the portion of the air interface whichcarries the actual data transmitted (e.g., the voice channel). Itoperates over frequencies separate from the DCCH, which are used forsignaling and control purposes. Since the WCS coexists with public macroor micro cellular networks, it monitors the RF channel activities,detect unused and interference-free channels, and makes channelselections and adjustments in real time for interference-free operation.

Another exemplary network architecture of the WCS is illustrated in FIG.2. The WCS system may be installed at the satellite site (e.g., CustomerSite B) 201 as well as the main site (e.g., Customer Site A) 202. When asubscriber is provisioned for service, the Customer Service Center (CSC)113 downloads the subscriber's profile to all NSPs 106 (e.g., 106A and106B). The subscriber is allowed to roam between the customer sites 201and 202. In one exemplary embodiment, the NSPs 106A and 106B areinterconnected through the provider Intranet 112, for example, AT&TIntranet. However, the NSP's 106A and 106B may be interconnected throughany secure virtual network from any provider.

In the WCS, a call is delivered by the Local Digital Switch 104A or 104Busing the DN. Unlike normal wireline phone services, however, thelocation of the WCS subscriber changes continuously with movement of theMS 101 within the service area. Therefore, a special intelligentdelivery mechanism using Advanced Intelligent Network (AIN) has beendeveloped for the WCS call delivery. In the AIN architecture, theService Switching Point (SSP), here the LDS 104A and 104B has thecapability of determining which calls require AIN services based on thedialed DN. The process of identifying calls that require AIN processingis known as “triggering,” since a particular characteristic of the call“triggers” the switch into providing AIN call treatment. So, when theDNs of ISDN telephone 109 or POTS telephone 108 are provisioned as WCSDNs, an incoming call to these DNs will prompt an AIN trigger. Once anevent causing a trigger occurs, a query message is sent to the ServiceControl Point (SCP) as illustrated in FIGS. 5, 6 and 7. The SCP is, forexample, NSP 106. Based on the information contained in the querymessage, the SCP (NSP 106A or 106B) determines which service is beingrequested and provides appropriate information to the LDSs 104A or 104B.In the exemplary WCS architecture, all the routing information is storedin the NSPs 106A and 106B. Therefore, the LDSs 104A and 104B in the WCSsends the query message to the NSPs 106A and 106B, and the NSPs 106A and106B directs the LDS 104A and 104B to deliver the call to itsappropriate destination. A detailed description of mobile stationregistration in the WCS follows.

III. Mobile Station Registration

FIG. 3 shows an exemplary embodiment of a registration process used toregister a MS 101 when the MS 101 enters a WCS service region (e.g.,customer site B 201). Upon entering the WCS system service area, the MS101 automatically registers with the NSP 106 serving that customer site.The NSPs 106A and 106B contain the subscriber profiles distributed bythe Customer Service Center 113 (CSC). The NSP (204A or 204B) handlingthe call then validates the MS 101 by examining the subscriber profilefor that MS 101. If the subscriber is roaming to another Customer Site,the Serving NSP 106B notifies the Home NSP 106A that the subscriber isregistered in its (Serving NSP's 106B) service area.

In particular, when the MS 101 is powered on, an IS-136 Registrationmessage 307 is sent to the VAP 103. The VAP 103 then forwards theregistration notification message 308 to the serving NSP 106B. Theserving NSP 106B validates the subscriber by looking up the subscriberinformation stored locally and previously downloaded from the customerservice center (CSC) 113. If the NSP 106 was not the subscriber's HomeNSP 106A, then a registration notice message REGNOT 309 would be sent tothe Home NSP 106A for the MS 101 indicating that MS 101 was registerednow in serving NSP 106B's area. The Home NSP 106A would then store theroaming information of the MS 101, and send regnot message 310 to theServing NSP 106B for acknowledgment. However, with the assumption thatthe Home NSP 106A was indeed the actual Home NSP of the MS 101, then theHome NSP 106A sends a regnot message 310 to Serving NSP 106B. If theHome NSP 106A found that the MS 101 had been registered at another NSP,e.g., Old NSP 106C, and had left without proper de-registration, thenthe Home NSP 106A would send a registration cancellation messageREGCANC, 311, to cancel the previous registration at the Old NSP 106Cfor confirmation. The Old NSP 106C would then remove the records for theMS 101 from its memory, and send a registration cancellation responsemessage, regcanc, 312, back to the Home NSP 106A. However, assuming thatHome NSP 106A had sent the regnot 310 message to Serving NSP 106B, thenServing NSP 106B would send a registration acceptance message,Registration Accept, 313, to VAP 103. The VAP 103 then informs MS 101that the registration is completed, by sending IS-136 registrationacceptance message, Registration Accept 314, to MS 101. This completesthe registration process for MS 101. Registration in the MS 101 Home NSP106A is simpler requiring only steps a and d illustrated in FIG. 3.

IV. Call Origination from a Mobile Station

FIG. 4 shows an exemplary call origination from a MS 101 directed to aPSTN 125 DN. When the subscriber MS 101 places a call via an originationmessage, IS-136 Origination 407, the VAP 103 first checks the validityof the MS 101 with NSP 106 via Origination Request 408. The NSP 106 thenprovides the VAP 103 with an Origination ACK 409 message indicating thatthe MS 101 is recognized and the VAP 103 may go forward with the callorigination. After that, the VAP 106 sets up an ISDN connection, ISDNSet up 410, to LDS 104. The LDS 104 performs the dialed digit analysisand proceeds with the call delivery procedures concluding in a connectedcall to the PSTN 125 DN.

More specifically, the MS 101 dials a DN number and sends an IS-136Origination 407 message to VAP 103. VAP 103 then sends an OriginationRequest 408 message to NSP 106. After checking the appropriate databasesto determine if the MS 101 is a valid registered subscriber, NSP 106returns an Origination ACK 409 message to VAP 103. The VAP 103 thenreserves a RF DTC channel and sends an ISDN Q.931 Setup 410 message tothe LDS 104. The LDS 104 then performs a dialed digit analysis and sendsan ISUP IAM 411 message to a far end switch in the PSTN 125 forend-to-end connectivity. The LDS 104 also sends an ISDN (Q.931) CallProceeding 412 message to the VAP 103. The VAP 103 then sends an IS-136Digital Traffic Channel (DTC) Designation 413 message to the MS 101 sothat MS 101 may then tune to the designated traffic channel. MS 101indicates to VAP 103 that it is using the designated DTC by respondingwith an MS on DTC 414 message. The VAP 103 then detecting that the MS101 is tuned to the designated traffic channel, cuts through the voicepath between RF DTC channel and ISDN B channel.

After receiving the ISUP ACM 415 message from the destination switch inthe PSTN 125, the LDS 104 sends an ISDN Alerting 416 message to VAP 103.Next, the Ringback Tone 421 is delivered to the MS 101 from thedestination switch. When receiving ISUP ANM 417 message from the PSTN125, the LDS 104 sends an ISDN Connect 418 message to VAP 103, removesthe ringback tone, and cuts through voice path 422. The VAP 103 thensends an ISDN Connect ACK 419 message back to the LDS 104. Afterconnection of the voice path 422, the VAP 103 sends a Connected 420message to the NSP 106 for billing and other OAM&P purposes.

V. Incoming Call Termination

Exemplary call flow diagrams illustrating various call termination(incoming call connection) scenarios for the WCS system are illustratedin FIGS. 5 through 7. When provisioning the necessary parameters for thesubscriber, the WCS subscriber's DN is provisioned for the AINTermination Attempt Trigger (TAT) so that the subscriber's mobilestation is the first destination determined for incoming calltermination. Consequently, when a call to the subscriber's DN isreceived, it triggers the LDS 104 to send a call treatment query messageto the NSP 106. The TAT call treatment procedure in the NSP 106 willdirect the LDS 104 to deliver the call to its appropriate destination.The DN in the VAP 103 that is used to deliver the call to the MS 101 isreferred to as the Forward Directory Number (FDN).

Depending on the first call delivery destination, there may be twodifferent call termination scenarios. The first scenario involvesdelivering the call first to a tip ring (T/R) desktop phone 108 (POTs)or an ISDN phone 109, while the second involves delivering a call firstto a mobile station 101. In each scenario, a different AIN trigger isutilized, and the call termination may be implemented using one of thetwo scenarios. The latter scenario of delivering the call to a mobilestation will be utilized to exemplify the procedure.

The TAT call treatment procedure in the NSP 106 will direct the LDS 104to deliver the call to the subscriber MS's current location. If there isno answer from the MS 101 phone, the call is delivered to thesubscriber's desktop phone (e.g., POTs 108 or ISDN 109). In oneexemplary embodiment, once the call is forwarded to the MS 101 DN (FDN),the call follows the Originating Call Model (OCM) rather than theTerminating Call Model (TCM), and an O_No_Answer trigger can be usedrather than a T_No_Answer trigger. In yet another embodiment, theT_No_Answer trigger could be used to deliver the call to the desk topphone first, and if the call goes unanswered, the trigger can be used torequest additional routing information from the NSP 106. The NSP 106would then locate the MS 101 and instruct the LDS 104 how to deliver thecall.

An exemplary call flow of a termination wherein the incoming call isrouted from the PSTN 125 to MS 101 is illustrated in FIG. 5. Aspreviously illustrated in FIG. 4, if the call is originated from the MS101 or desktop phone (e.g., 108 or 109) inside a region handled by thesame LDS 104, the resulting call flow would be similar, except thatthere will be appropriate ISDN Q.931 messages to and from the LDS 104instead of the ISUP messages between the PSTN 125 and the LDS 104. Thefollowing illustration shows an incoming call to a MS 101 that answersthe call.

The PSTN 125 user first dials the DN of a WCS subscriber. The LDS 104then receives an ISUP IAM 508 message from the PSTN 125. The LDS 104recognizes that the DN is provisioned for AIN Termination AttemptTrigger (TAT). The LDS 104 then suspends the delivery of the call andsends an AIN query message, TCAP (AIN termination attempt [DN]) 509, tothe NSP 106 for an appropriate routing instruction. The NSP 106recognizes that the subscriber's MS 101 is active in its serving area,and sends a page message, Page 510, to the VAP 103 serving MS 101. TheVAP 103 in turn sends an IS-136 Page 528 message to the MS 101. The MS101 responds to the IS-136 Page 528 via a IS-136 Page Response 529message destined to VAP 103. VAP 103 then sends a Page Response 511message to the NSP 106. The NSP 106 then directs LDS 104 to forward thecall to the Forward Directory Number (FDN), TCAP (AIN Forward_Call[FDN], NEL [O_No_Answer]) 512 of the VAP 103 serving the MS 101 (in aTCAP Conversation package). The NSP 106 also indicates its interest inevent (O_No_Answer for FDN) by sending next event list NEL[O_No_Answer]) 532 information to the LDS 104 in a Request componentthat accompanies the Routing component, in a conversation package. TheLDS 104 then starts a No Answer Timer (T(NoAnswer)) 531 for FDN andsends an ISDN (Q.931) Setup 513 message to the VAP 103. The VAP 103 thensends a Digital Traffic Channel (DTC) Designation 530 message to the MS101 along with an ISDN (Q.931) Call Proceeding 514 message to the LDS104. The MS 101 then tunes to the traffic channel and responds to theVAP 103 with MS 101 on DTC 515. The VAP 103 detects that the MS 101 ison the appropriate traffic channel. The VAP 103 then alerts MS 101 withan Alert-with-info 516 message and MS 101 acknowledges with a Mobile ACK517 message. The VAP 103 then sends an ISDN Alerting 518 message to LDS104.

Upon receiving ISDN (Q.931) Alerting 518 message, the LDS 104 then sendsan ISUP ACM message 519 to the switch in PSTN 125. In the meantime, theLDS 104 is sending a ringback tone 520 to the PSTN 125 caller. When theMS 101 answers (before T(No Answer) 531 expires), the VAP 103 sends anISDN Connect message 522 to the LDS 104 in response to the Connect 521message from MS 101. The LDS 104 then cancels T(No Answer) 531, andsends ISUP ANM 523 message to the PSTN 125 switch and cuts through thevoice path 527. After the LDS 104 sends an ISDN (Q.931) Connect ACK 524message to the VAP 103, it then sends TCAP (AIN Close) 525 message tothe NSP 106 (using TCAP Response) to complete the TCAP transaction.After receiving the ISDN (Q.93 1) Connect ACK message 524 from the LDS104, the VAP 103 sends Connected 526 message to the NSP 106 for billingand other OAM&P purposes. At this point, voice path 527 has beenestablished and the call proceeds between the PSTN 125 caller and the MS101 subscriber until it is ended and disconnected (e.g., hang up).

In accordance with the instant invention, FIG. 6 shows a process whereinan incoming call goes unanswered by the mobile station, e.g., MS 101,and the No Answer Timer 531 expires. Whenever, a call destined for a MS101 goes unanswered and the No Answer Timer 531 expires, the NSP 106will direct the call to the DN (telephone or VMS) which is associatedwith that MS 101.

The PSTN 125 user first dials the DN of a WCS subscriber. The LDS 104receives ISUP IAM 508 message from the PSTN 125. The LDS 104 willrecognize that the DN is associated with MS 101 and is provisioned forAIN Termination Attempt Trigger (TAT). The LDS 104 then suspends thedelivery of the call and sends an AIN query message, TCAP (AINTermination Attempt [DN] 509), to NSP 106 for an appropriate routinginstruction. The NSP 106 will recognize that the subscriber's MS 101 isactive in its serving area, and will send Page 510 message to the VAP103 serving MS 101. The VAP 103 in turns sends IS-136 Page 528 messageto MS 101. The MS 101 will respond to the IS-136 Page 528 message viaPage Response 529 message destined to VAP 103. The VAP 103 then sendsPage Response 511 message to the NSP 106. The NSP 106 then directs theLDS 104 to forward the call to the Forward Directory Number (FDN) of theVAP 103 serving the MS 101 (in a TCAP Conversation package) by sendingthe TCAP (AIN Forward Call [FDN], NEL [O_No_Answer]) 512 message to theLDS 104. The NSP 106 also indicates its interest in event O_No_Answerfor FDN by sending next event list (NEL) information to the LDS 104 in aRequest component accompanying the Routing component of a conversationpackage message 512. The LDS 104 then starts a No Answer Timer(T(NoAnswer)) 531 for FDN and sends ISDN (Q.931) Setup 513 message tothe VAP 103. The VAP 103 then sends Digital Traffic Channel (DTC)Designation 530 message to MS 101 and sends a ISDN (Q.931) CallProceeding 514 message to the LDS 104. The MS 101 then tunes to thedesignated traffic channel and sends the MS 101 on DTC 515 message toVAP 103. The VAP 103 then detects the MS 101 on the traffic channel andalerts the MS 101 with an IS-136 Alert-with-info 516 message the MS 101responds by acknowledging with a Mobile ACK 517 message. The VAP 103then sends ISDN Alerting 518 message to the LDS 104. Upon receiving theISDN (Q.931) Alerting 518 message, the LDS 104 then sends an ISUP ACM519 message to the switch in PSTN 125. In the meantime, the LDS 104 issending a ringback tone 520 to the caller.

In this case, the MS 101 does not answer the call and the No AnswerTimer T (No Answer) 531 expires. The LDS 104 then sends AIN O_No_Answer625 message to the NSP 106 in a conversation package. The NSP 106 sendsa TCAP (AIN Analyze_Route [DN]) 626 message to the LDS 104. Then the LDS104 sends a TCAP (AIN Termination_Attempt [DN]) 635 message back to theNSP 106, which authorizes the call termination to the DN by sending anTCAP (AIN Authorize_Term) 636 message to the LDS 104. The LDS 104 thensends an ISDN (Q.931) Disconnect 627 message to the VAP 103. The VAP 103then sends a Release 628 command to the MS 101 and the MS 101 stopsringing (buzzing or alert the user). The MS 101 then sends Mobile ACK629 back to the VAP 103. The VAP 103 now sends ISDN (Q.931) Release 630message to LDS 104 to notify the LDS that MS 101 is no longer beingalerted of the incoming call. The LDS 104 then sends ISDN (Q.931)Release Complete 631 message to the VAP 103 allowing MS 101 to be usedfor other calls or messages. When the NSP 106 instructs the LDS 104 toforward the call to the DN 626, the call processing is assumed by theLDS 104 as a normal call delivery in step 632. If the user subscribes toVMS 107, then after a certain number of rings, the LDS 104 will transferthe call to the VMS 107. The incoming call will thus be forwarded to thetelephone (ISDN 109 or POTS 108) associated with the DN being called.

In accordance with the instant invention, an exemplary methodology ofterminating an incoming call to a roaming subscriber located in anotherLDS area is illustrated in FIG. 7. The WCS subscriber's DN isprovisioned for the AIN Termination Attempt Trigger (TAT) so as to seekout the subscriber's MS first. In general, when a call to thesubscriber's DN arrives at the LDS 104, the call triggers the LDS 104 tosend a call treatment query message to NSP 106. The NSP 106 willrecognize that the MS 101 is currently registered in another CustomerSite (different LDS area) and will request a Forward Directory Number(FDN) from the visited area, Serving NSP 106B. The Serving NSP 106B thenchecks the current location of the MS 101 and the availability ofcircuits to handle the call and returns an FDN to the Home NSP 106A.After receiving the FDN, the TAT call treatment procedure in the HomeNSP 106A directs the LDS 104A to deliver the call to the FDN. Aftersending the ISUP IAM to the FDN, the Serving LDS 104B delivers the callto the VAP 103 presently serving the MS 101.

More particularly, a call termination occurs as follows when a MS 101 isroaming to another Customer Site, e.g., Site B 201, when the MS 101 hasa home location within Customer Site A 202. The PSTN 125 user dials aWCS subscriber's DN associated with a subscriber in Customer Site A. TheHome LDS 104A (LDS-A) receives an ISUP IAM 709 message from the PSTN125. The LDS-A 104A finds that the DN is provisioned for AIN TerminationAttempt Trigger (TAT) and suspends the delivery of the call, sending AINTermination_Attempt Query 710 message to the NSP-A 106A for anappropriate routing instruction. The NSP-A 106A will recognize that thesubscriber is not presently registered in its serving area but is nowregistered in Customer Site B 201. The NSP-A 106A will send ROUTREQ 711message to the Serving NSP (NSP-B) 106B. After receiving the ROUTREQ 711message, the NSP-B 106B sends Page 712 message to the VAP 103 presentlyserving the MS 101. The VAP 103 will then send an IS-136 Page 713message to the MS 101 and the MS 101 will respond with an IS-136 PageResponse 714 message destined for the VAP 103. The VAP 103 will thensend the Page Response 715 message to the NSP-B 106B. The NSP-B 106Bwill confirm the current location of the MS 101, and return the ForwardDirectory Number (FDN), in the routreq 716 message to the NSP-A 106A.The NSP-A 106A will then direct the LDS-A 104A to forward the call toFDN in Customer Site B via a TCAP (AIN Forward_Call [FDN],NEL[O_No_Answer]) 717 message. The LDS-A 106A then forwards an ISUP IAM[FDN] 718 message to the LDS-B 104B. After receiving the ISUP IAM [FDN]718 message, LDS-B 104B then sends an ISDN (Q.931) Setup 719 message tothe VAP 103 serving the FDN. VAP 103 sends the DTC Designation 720message to the MS 101, and then sends an ISDN (Q.931) Call Proceeding721 message to the LDS-B 104B. When the MS 101 tunes to the DTC it sendsan MS on DTC 722 message to VAP 103 and VAP 103 responds with anAlert-with-info 723 message. The MS 101 will then send a Mobile ACK 724message to the VAP 103 and the VAP 103 will then send an ISDN (Q.931)Alerting 725 message to the LDS-B 104B. The LDS-B 104B will then send anISUP ACM 726 message to the LDS-A 104A, which will in turn forward aISUP ACM 727 message to the switch in PSTN 125. The LDS-B 104B providesthe Ringback Tone 728 to the caller.

When the MS 101 answers, the MS 101 will send Connect 729 message to theVAP 103. The VAP 103 will then send an ISDN (Q.931) Connect 730 messageto the LDS-B 104B. The LDS-B 104B will then send an ISUP ANM 731 messageto the LDS-A 104A, which then forwards ISUP ANM 733 to the switch inPSTN 125, and an ISDN Connect ACK 732 message to VAP 103. Afterreceiving an ISDN (Q.931) Connect ACK 732 message from LDS-B 104B, theVAP 103 will send a Connected 734 message to the NSP-B 106B for billingand other OAM&P purposes.

If the MS does not answer, the call is delivered to the desktop phone orto the VMS 107 if the MS 101 subscriber has voice mail capabilities, bythe same mechanism using the NEL [O_No_Answer], as in the non-roamingcase (see FIG. 6). Otherwise, at this point, voice path 735 isestablished.

VI. Intra-LDS Mobile Station Assisted Handoff

In accordance with the invention, an exemplary embodiment of anintra-LDS mobile assisted handoff(MAHO) process is illustrated in FIG.8. The signaling flow in FIG. 8 discloses the handoff of a call betweenthe VAPs (e.g., VAPo 103A and VAPn 103B) served by the same LDS 104. Thesmooth/lossless handoff is accomplished by using the Directed CallPickup with Barge-in (DPU) feature supported by many switches. Adiscussion of the process follows.

While a call 806 involving the served MS 101 is in progress, the VAPo103A detects a handoff condition based on the measured channel qualitiesand their threshold value. The VAPo 103A initiates a Measurement order807 destined for MS 101. The MS 101 then responds to the Measurementorder 807 with a Measurement order ACK 808 and a Channel Quality Message809 destined for VAPo 103A. When VAPo 103A detects a handoff condition,it then sends a Handoff Request 810 to the NSP 106 with a list ofcandidate channels. The NSP 106 then selects the best candidate channel,identifies VAPn 103B as serving the channel, and sends a HandoffPreparation [MSID, DN-VAPo] 811 message to VAPn 103B.

Upon receiving the order from NSP 106, VAPn 103B reserves a B-channeland a RF channel for the MS 101, and establishes a 3-way call using theDPU feature. VAPn 103B then sends ISDN (Q.931) Setup [Feature Activation(DPU), DN-VAPo] 812 message to LDS 104. LDS 104 then returns an ISDN(Q.931) Call Proceeding 813 message to the VAPn 103B, followed by anISDN (Q.931) Connect 814 message. The VAPn 103B then responds to the LDS104 with an ISDN (Q.931) Connect ACK 815 message. The VAPn 103B thensends a Handoff Directive 816 message to VAPo 103A. The VAPo 103A thensends the Handoff order 817 to the MS 101 requesting MS 101 to retune tothe new RF channel of VAPn 103B, and disconnects its ISDN connection tothe LDS 104 as shown in steps 818-823. The MS 101 is then placed on thenew channel with VAPn 103B per step 824. The VAPn 103B sends a messageHandoff Result 825, to the NSP 106, which indicates that the MS 101 hassuccessfully been handed off to the new channel, indicated as handoffcomplete.

In yet another embodiment of the invention, a user on a wirelinetelephone call can have the capability of transferring that call tohis/her cellular/PCS MS. In accordance with this feature, a user on awireline telephone with an active call may enter a special feature code,such as *99, in order to activate the feature.

The following is a more detailed description of an exemplary intra-LDSmobile assisted handoff as previously described and as depicted in FIG.8. Initially, there is an existing call involving the served MS 101 inprogress. The VAPo 103A sends a Measurement order 807 over the FACCH tothe MS 101 to measure the BER (bit error rate) and RSSI (receivedsignal/strength indicator) of the current channel and the RSSIs of otherRF channels. The MS 101 acknowledges the Measurement order 807 bysending a Measurement order ACK 808 over the FACCH. The MS 101 thenperforms the channel quality measurements in response to the Measurementorder 807 and sends a Channel Quality message 809 to the VAPo 103A.

Next, the VAPo 103A detects a handoff condition based on the receivedChannel Quality Message 809 and the associated threshold values. TheVAPo 103A then sends a Handoff Request 810 message to NSP 106 with alist of candidate channels, and immediately starts its handoff requesttimer (T1). Upon receiving the Handoff Request 810 from the VAPo 103A,the NSP 106 selects the candidate with the strongest RSSI. The NSP 106then checks if the resources (ISDN B-channel and RF channel) areavailable for the candidate channel, and identifies VAPn 103B as the newVAP which will serve the MS 101. The NSP 106 then sends a HandoffPreparation 811 message, including the serving MSID and DN-VAPo (the DNof VAPo 103A, i.e., the phone number to be barged in on) to VAPn 103Band immediately starts its handoff preparation timer (T2). In responseto the Handoff Preparation 811 message, VAPn 103B then reserves aB-channel and a RF channel for the MS 101 and starts to establish a3-way call using a DPU process in the following manner. The VAPn 103Bsends a ISDN (Q.93 1) Setup 812 message to LDS 104, which includes aFeature Activation code for DPU and DN-VAPo. The LDS 104 then sends theISDN (Q.931) Call Proceeding 813 message back to the VAPn 103B followedby an ISDN (Q.931) Connect 814 message when the call is connected toDN-VAPo. The VAPn 103B then sends the ISDN (Q.931) Connect ACK 815message to LDS 104. The VAPn 103B then sends a Handoff Directive message816 to the VAPo 103A. The VAPo 103A cancels the T1 timer, and sends theHandoff order 817 to the served MS 101 over the FACCH, requesting the MS101 to retune to the new RF channel (along with other channel assignmentinformation). The MS 101 then acknowledges the Handoff order with aHandoff ACK 818 to VAPo 103A. Upon receiving the Handoff ACK 818, theVAPo 103A then disconnects the B channel connection by sending an ISDN(Q.931) Disconnect 819 message to LDS 104. LDS 104 then sends an ISDN(Q.931) Release 820 message to the VAPo 103A, and the VAPo 103Aacknowledges the Release Message 820 and disconnection of the previouscall by sending the ISDN (Q.931) Release Complete message 821 to the LDS104. The VAPo 103A tears down the voice path connection that it hadestablished for the MS 101. The VAPo 103A sends the Handoff Complete 822message to the NSP 106, which includes the time information of theserving MS 101 for billing and other OA&M purposes. The LDS 104 thenstarts its handoff complete timer (T3). The NSP 106 responds by sendinga Handoff Complete ACK 823 to VAPo 103A, and VAPo 103A cancels T3. TheMS 101 then retunes to the new channel of the VAPn 103B. Afterconfirming that the MS 101 has been retuned to the new channel, the VAPn103B then sends a Handoff Result 825 message to the NSP 106, whichindicates that the MS 101 has been successfully handed off to a newchannel and timer T2 is cancelled. The NSP 106 acknowledges the handoffcomplete to both the LDS 104 and the VAPn 103A, using handoff complete826 message.

VII. WCS as a Wireless PBX System

In yet another embodiment of the instant invention, there exists awireless centrex service platform which is a Wireless PBX system (WPS)offering a wireless access system with customer site wireline ISDNcapable PBX to provide integrated wire and wireless voice access. In oneapplication of the system, a WPS as disclosed could be used to enhancethe PrimeXpress service offered Teleport Communications Group (TCG, nowowned by AT&T). This system could advantageously provide acordless-like, anywhere, anytime communication in any indoor, businessand campus environment using subscriber's macrocellular/PCS mobilestation (MS 101). In accordance with the invention, the WPS systemincludes an Intelligent Wireless Controller (IWC) system 902, itssubtending Voice Access Ports (VAPs) 103 and the customer site ISDNcapable PBX 901.

Additionally, the WPS also functions as an integrated wireline andwireless system without being connected to any public macro cellularsystem. Therefore, it does not support mobility management and roamingbetween WPS and the public macro cellular and PCS networks. In anotherembodiment, the WCS can connect the NSP 106 to a macrocellular SS7network to support integrated mobility functions including terminalhandoff and personal roaming features.

Further, the WPS provides location and mobility management for the WVPSsubscriber's mobile station (MS 101) inside the WPS serving area.

After a simple registration process, the WPS subscribers use theirIS-136 digital TDMA cellular/PCS phone 101 as a cordless-like phone inthe WPS service area without incurring air-time charges. The dual ringfeature of the MS 101 allows the user to receive calls anywhere insidethe WPS service area. As a result, whenever a user is called at his/herstationary phone 108 attached to the customer premises PBX 901, the WPSsystem simultaneously locates and alerts the user's IS-136 phone 101. Ifthe user does not answer MS 101, the Voice Message System 109 associatedwith the customer premises PBX 901 will answer the call. In thisembodiment, calls from the stationary phone 108 or the IS-136 phone 101are directed to the customer site PBX and processed by the TCGPrimeXpress Services. Essentially, the PrimeXpress service is anoutbound trunk to a switch 904, such as the Lucent 4ESS, that bypassesthe local switch. In the exemplary WPS system, call features include,but are not limited to, Short Message Services (SMS) and/or paging(IS-136 feature); PBX interworking, including premises dialing plan,closed-user-group, and dual ringing of stationary and MS phones;wireline call features, such as three way calling, call forwarding, calltransfer, caller ID, call waiting, messaging and voice mail services;support for voice privacy; and cordless-like service without air timecharges.

In the embodiment of the invention illustrated in FIG. 9, there existsan ISDN PRI interface 7, an IS-136 air interface 3, and an ISDN BRIinterface 2. The ISDN BRI 2 interconnects VAP 103 and the IntelligentWireless Controller 902. Call processing messages for call setup, callteardown, feature applications and OAM&P messages are carried on thedata D-channel in X.25 packets. In addition to carrying call processingmessages, the D-channel also carries ISDN (Q.931) signaling for callsetup and teardown of the voice connection on the bearer B-channel. TheIS-136 air interface 3, provides communication between the VAP 103 andthe MS 101. The ISDN PRI interface 7 interconnects the IWC 902 and thecustomer premise PBX 901 and utilizes Q.931 signaling. The wirelesscommunications controller's call processing messages for call setup,call teardown, feature applications and OAM&P messages are carried inthe D-channel to the NSP 106. The D-channel also carries the Q.931messages for the voice connections on the B-channels between the VAP 103and the IWC 902. In one embodiment of the Intelligent WirelessController (IWC), there exists an ISDN switch 903 and a controllercircuit.

VIII. Wireless Voice and Data WCS

In yet another embodiment of the instant invention, there is a WirelessCommunication Service Platform that offers an economical and highperformance wireless access network, for satisfying the need for anin-building integrated voice and data system providing mobility. Whilethe exemplary platforms previously disclosed are focused on providingvoice capabilities, this embodiment discloses a platform for providingdata support integrated with voice capability. There exist at least oneData Access Port (DAP) (e.g., DAP 1001A or DAP 1001B), which is amicro-cellular base station that uses the CelluLAN™ Common Air Interface(IEEE802.11) for high density and seamless in-door coverage providing 4to 10 Mbps data rate for data applications.

The architecture of the DAP is similar to that previously disclosed forthe VAP, and uses digital software radio technology which providessuperior RF performance, along with RF based self configurationalgorithms for “stacked spectrum” operation. A 10BaseT or 100BaseT LocalArea Network (LAN) 1007 connects the DAPs, as well as other LAN devicessuch as servers, and or local printers, to the Integrated WirelessCommunication Controller 1002 (e.g., Integrated Enterprise WirelessCommunication (EWC) Controller). In one exemplary embodiment of theIntegrated Wireless Communication Controller, the wireless voice anddata services are integrated by bundling the PSTN/voice traffic on atrunk 7 to the LDS 104, e.g., 5ESS, and switching the data traffic to anATM network 1005 for internet/intranet access (ISP 1006). The data andvoice could be switched by any suitable means commonly known in the artsuch as packet switching or circuit switching. A laptop 1003A or 1003Bwith a PCMCIA card that supports CelluLAN™ CAI, can access the LAN 1007anywhere inside the building. After the laptop 1003A or 1003B hasregistered with the LAN 1007, the user can access other PCs, laptops,and or other servers on the LAN, the intranet, and the internet. Theuser can access this LAN in his office, meeting rooms, the cafeteria, orany area of the building covered by DAPs. Once implemented, the instantinvention would provide the advantage of eliminating the need to wire anindividual office for data and/or voice connectivity. The wirelesscommunication service platform would potentially improve overallproductivity by giving the users access to their desktop anywhere,anytime. In other words, the instant invention would provide a “desktopto go” environment that would support “moment of value communications”at the time needed when information is most critical.

In accordance with the invention, there exists a Data Access Ports(DAPs) 1001A and 1001B interconnected to an Integrated WirelessController 1002, via interface 8. Interface 8 is a standard 10/100 BaseTEthernet connection. This is advantageous in that it provides a flexibleinterface so that data can be routed via the ethernet interface to awired LAN or through an ATM network interface 10 to an ATM network 1005interconnected to an Internet Service Provider (ISP) 1006. The IEEE802.11 air interface 9 provides a wireless access to the DAPs 1001A and1001B. The Data Access Port has exemplary capabilities such as, a highspeed LAN access from 4-10 Mbps data rate using the CelluLAN™ CAI; an IPaddress assignment during registration; seamless mobility managementincluding roaming and intra/inter LAN handoffs; data privacy functionsto support standard security algorithms; communication support betweenDAPs and VAPs for SMS, email, paging, and data; and SNMP for OA&M.

The exemplary Integrated Wireless Communications Controller 1002 is asingle platform controller with Premises Interfaces providing ISDN BRIinterfaces 2 and Ethernet interfaces 8 for the VAP and DAP,respectively, and Network Interfaces providing ISDN PRI 7 and ATM forPSTN and ATM network access 10, respectively. The exemplary ATM networkinterface 10 is data only, and the Ethernet interface can also be usedto connect to a wired Local Area Network (LAN). In accordance with theinvention, there exist an ISDN PRI interface 7, interconnecting theIntegrated Wireless Communications Controller 1002 with a LDS 104. Inaccordance with the invention, the LDS 104 interconnects to a RDT 102, aNSP 106 and to trunks connected to networks such as the AT&T Local andLong Distance Network 110, the PSTN 125, and the SS7 network 111.

IX. Feature Activation/Deactivation

The present invention includes means for feature/functionactivation/deactivation which is controlled by user input. The NSP 106contains a dynamic user profile database stored in a memory (see FIG.12, memory 1240) used to, for example, determine whether a mobilestation is authorized to use a particular WCS feature/function andwhether the feature/function, if available, is active.

FIG. 11 illustrates a general signaling flow applicable for both featureactivation and feature deactivation for the features/functions of thepresent invention that require activation/deactivation when MS 101 isidle (MS 101 camping on DCCH). Although FIG. 11 does not illustrate anRDT 102, it is understood that an RDT 102 may be included in oneembodiment and located between the VAP 103 and the LDS 104. While an MS101 registered with an NSP 106 is idle, the MS 101 user may dial thefeature activation/deactivation code (e.g., *66, representing anactivation code for an automatic callback feature/function) and press,for example, the “send” button on MS 101. In response, an IS-136Origination [Feature Code] 1101 message (where the entered numberfeature activation/deactivation code is entered rather than a calledparty number) is sent to VAP 103 via the DCCH (over-R-DCCH). An IS-136Serial Number message 1102 also is sent to VAP 103. After receiving themessage, the VAP 103 sends an Origination Request [Dialed Digit]. 1103message to NSP 106 and starts the TO1 timer. Alternatively, featureactivation can be achieved when the MS 101 is active. For example,during an active call the MS 101 user may merely enter the feature codeand the feature will be activated.

After receiving the Origination Request [Dialed Digit] 1103 message, theNSP 106 analyzes the dialed digits using, for example, controller 1230(see FIG. 12). If the dialed digits includes a feature activation code,the NSP 106 checks the Wireless Centrex System Database (WCSD) (forexample a user mobile station service profile database stored in memory1240 (see FIG. 12)), using the Mobile Station Identification (MSID) todetermine if MS 101 is authorized for the particular feature requested.If the MS 101 is authorized for the feature requested, featurevalidation is successful and the NSP 106 activates the feature for thesubscriber and stores any associated feature information into the userprofile database. The NSP 106 then sends an Origination NACK [Cause,Display] 1104 message with the Cause equal to Feature Activation and theDisplay information indicating successful feature activation, back tothe VAP 103 (e.g., Origination NACK [Feature Activation Successful, Callforwarded to FwdDN]).

On the other hand, if the dialed digits are a feature deactivation code,the NSP 106 checks the WCSD to see if that particular feature is active.If the feature is active, the NSP 106 deactivates the feature andremoves any associated feature information from the WCSD. The NSP 106then sends an Origination NACK [Cause, Display] 1104 message with theCause equals to Feature Deactivation and the Display informationindicating a successful feature deactivation, back to the VAP 103. TheNSP 106 generates an Origination NACK message rather than an OriginationACK message because the feature activation request is provided to theNSP 106 in a message (Origination Request 1103) that is generallyintended for use in originating a telephone call and when a featureactivation/deactivation is requested when the MS 101 is idle, no callwill be complete since no DN was entered, thus, the response by the NSP106 with a none acknowledgement message, Origination NACK 1104. However,the Origination NACK 1104 message does contain information in its Causeand Display fields that is needed to inform the MS 101 user that afeature has been activated or deactivated correctly.

In either feature/function activation or feature/function deactivation,the VAP 106 then cancels the TO1 timer and issues an IS-136Reorder/Intercept [Display] 1105 message with the Display informationover the Paging Channel (PCH) to the MS 101. The IS-136Reorder/Intercept [Display] 1105 message is similar to the OriginationNACK 1104 message in that it is generally an indication message that acall origination request has been unsuccessful and is used in this caseas a vehicle for providing the MS 101 user information regarding thestatus of their feature activation/deactivation. After receiving themessage, MS 101 displays the text message from the Display informationfield on MS 101 (e.g., Call forwarded to FwdDN) and resumes the DCCHidle (camping) state. A more detailed description of thefeature/function activation/deactivation processing that goes on in theNSP 106 and VAP 103 using the call forward feature/function as anexample follows.

After the NSP 106 receives the Origination Request [Dialed Digit] 1103message with the Dialed Digit equal to the Call Forward featureActivation/Deactivation code, the NSP 106 first performs an analysis ofthe dialed digits to determine if it is a valid featureactivation/deactivation code. Next, the NSP checks the user serviceprofile in the WCSD, using the MSID of the originating MS 101, todetermine if the originating MS 101 is authorized for the requested CallForward feature. The NSP 106 also verifies that the parameters for thefeature code are valid. If this validation process is successful, theNSP 106 updates its memory pertaining to feature activation/deactivationfor the particular MSID and sends an Origination NACK [Cause, Display]1104 message to the VAP 103 with the Cause field equal to Call ForwardFeature Activation/Deactivation Successful and the Display fieldinformation equal to Call forwarded to FwdDN (the forwarding DN dialedwith feature code), indicating that feature activation/deactivation issuccessful.

The NSP 106 will take the following actions in response to the MS 101user entering various codes and different phone numbers to forward acall. As a first alternative, when the feature/function CallForwarding—Unconditional is entered on MS 101 by the WCS subscriber theNSP 106 checks to see if there is a Call Forwarding feature/functionalready active for the particular mobile station MS 101. If a CallForwarding feature/function is already active then the NSP 106 willupdate the previous feature/function active code entry and update, forexample, the information with a new call forwarding number. Otherwisethe NSP 106 will simply create a new feature/function active code entryand the call forwarding number for the mobile station MS 101.

As a second alternative, if the mobile station MS 101 user enters thefeature/function code for the Call Forwarding—Programmable Ring featureand the number of rings is specified, the NSP 106 will verify that thenumber is within a range of acceptable values (i.e., valid). If thenumber of rings is not a valid number, the NSP 106 will use a defaultvalue for the number of rings to use. Next, the NSP 106 will translatethe number of rings into an associated number of seconds it will take toexecute the desired number of rings and create or modify as necessarythe feature entry for the mobile station MS 101 to provide the desirednumber of seconds for ringing. Thus, this entry will contain the MSID,call forwarding number and the number of seconds ringing is to continue.

As a third alternative, if the mobile station MS 101 user enters thefeature/function code for the Call Forwarding—Time of Dayfeature/function, the NSP 106 will verify that the begin time and endtime parameters are present and valid. If the time parameters are valid,the NSP 106 will create/modify the feature entry for the mobile stationMS 101. The entry will contain MSID, call forwarding number, begin timeand end time.

As a fourth alternative, if the mobile station MS 101 user enters thefeature/function code for the Call Forwarding—Busy feature/function, theNSP 106 will modify or create the feature entry for the mobile stationand store the call forwarding number to be used if an incoming calloccurs when the mobile station MS 101 user is, for example, on anothercall. The entry will contain the MSID, the call forwarding number, and aflag indicating that the call is to be forwarded when the MS 101 line isbusy.

Furthermore, the MS 101 user may activate a feature, such as callforward, for a particular DN without entering the DN. First, aspreviously noted, the MS 101 could enter the feature code while on anactive call and the feature would be provisioned relative to the DN ofthe other party involved in the call. Second, feature activationprovisioning may be achieved without entering a DN by entering thefeature activation code immediately after a call has been disconnected.

However, if the mobile station MS 101 user enters the feature/functioncode for Call Forwarding Feature Deactivation, the NSP 106 will verifythat the feature corresponding to the deactivation code is currentlyactive for the mobile station MS 101. The NSP 106 will then deactivatethe feature/function and delete the associated feature information fromthe subscriber profile.

In any case, the NSP 106 will subsequently send out the Origination NACK[Cause, Display] 1104 message to the VAP 103. The Cause field willcontaining information such as; Feature Activation Successful, FeatureActivation Failed, Invalid MS, Out of Resource, Input Unknown, FeatureDeactivation Successful, Feature Deactivation Failed. The Display fieldwill contain information such as Call forwarded to FwdDN.

Some examples of possible feature activation and deactivation codes areprovided in the tables below for various WCS feature/functions. Theactivation and deactivation codes for the WCS features/functions, whichneed to be activated/deactivated when the MS is idle (MS 101 on DCCH),are tabulated below.

TABLE 1 Deactivation Feature Application Activation Code Code AutomaticCallback *66 *660 or MS power down/de- registered CallForwarding-Unconditional *90#DN *900 Call Forwarding-Programmable*91*x#DN, *91#DN *910 Ring Call Forwarding-Time of Day *92*hhmm*hhmm#DN*920 Call Forwarding-Busy *93#DN *930 Call Return *69 *690 Call Screen*60#DN or *60#n#DN *600#DN Distinctive Ringing *70#DN or *70#n#DN*700#DN Speed Calling *75*(1-30)#DN

In the Table 1 above, the DN denotes a directory number (telephonenumber), the x denotes the number of rings and the hh denotes the hourof day in the format of 00 to 23, mm denotes the minute in the format of00 to 59.

The feature codes of WCS features/functions, which can be initiated whenthe call is in progress (MS 101 on DTC), are tabulated below in Table 2.

TABLE 2 Feature Application Feature Code Call Transfer *77#TransferDNThree-way call *33#ThreeWayDN

One skilled in the art will recognize that the feature/functionactivation and deactivation codes provided above are purely exemplaryand may be different without changing the basic concept of the presentinvention.

Furthermore, as examples of feature/function activation/deactivation,the NSP 106 will take the following actions for various differentfeature/function codes input by the MS 101. (1) CallForwarding—Unconditional: If there is a Call Forwarding feature alreadyactive for the particular mobile, the NSP 106 will update the featureentry with the new call forwarding telephone number. Otherwise, the NSP106 will create a new feature entry for the mobile. (2) CallForwarding—Programmable Ring: If the number of rings is specified, theNSP 106 will verify that the number is within the range, or it will usethe default value. The NSP 106 will translate the number of rings intonumber of seconds and create/modify the feature entry for the MS 101.The entry will contain the MSID, call forwarding number and the numberof seconds. (3) Call Forwarding—Time of Day: The NSP 106 will verifythat the begin time and end time parameters are present and valid. Ifthe time parameters are valid, the NSP 106 will create/modify thefeature entry for the MS 101. The entry will contain MSID, callforwarding number, begin time and end time. (4) Call Forwarding—Busy:The NSP 106 will modify/create the feature entry for the MS 101 andstore the call forwarding number. (5) Speed Dialing: NSP 106 will verifythe data that is sent by the MS 101 for provisioning. The unique codespecified may be, for example, a valid number in the range 1-30, and theDN may be, for example, a number consisting of 1 to 17 digits (a singledigit number can be the smallest number that a WCS subscriber can dialto make a successful call, e.g., dial 0 to reach the operator. Seventeendigits may be required to accommodate a call screen for internationalcalls. To make an international call—dial 9 to get out, then 3 numbercode to make an international call, 2/3 number code for the country, 2/3number code for the region/area and 7 digit phone number, makes apossible total of 17 digits). The NSP 106 then updates the speed-dialingcode list for the MS 101 with the new data provided. In case an entryfor the requested unique code already exists, then the current DN willoverwrite the existing entry. (6) Call Screen: NSP 106 will verify thedata that is sent by the MS 101 for provisioning. The CallScreenDNspecified must be a valid number, e.g., it may consist of 4 to 10digits, and the code signifying the type of treatment may be, forexample, from 1 to 3. The NSP 106 then updates the CallScreenDN list forthat MS 101 with the new data provided. (7) Distinctive Ringing: If theuser sends *70#n#DN, where n is a number from 1 to 5 and DN is a phonenumber and presses the send button, NSP 106 will verify the data that issent by the MS 101 for provisioning. The DistinctiveRingingDN specifiedmay be, for example, a valid number consisting of 4 to 15 digits, andthe code signifying the type of ring signal may be, for example, between1 and 5. The NSP 106 then updates the DistinctiveRingingDN list for thatMS 101 with the new data provided. (8) Feature Deactivations: The NSP106 will verify that the feature corresponding to the deactivation codeis currently active for the MS 101. It will then delete the associatedfeature information from the subscriber profile.

In any case, if the validation is unsuccessful because the feature codeis invalid or the parameters are missing, a Cause value equal to theFeature Activation/Deactivation Failed and the appropriate Displayinformation regarding the specifics of the failure will be included inthe Origination NACK [Cause, Display] 1104 message.

When VAP 103 receives the Origination NACK [Cause, Display] 1104message, the VAP 103 cancels the timer TO1, extracts the Displayinformation from the message, and inserts the Display information intothe Display field of IS-136 Reorder/Intercept [Display] 1105 message.Next, the VAP 103 send the IS-136 Reorder/Intercept [Display] 1105message to MS 101 and instructs the MS 101 to return to the idle(camping) state. Similar feature/function activation/deactivation signalflows will be used in the various feature/functions for the WCS asdescribed in more detail below.

Although the feature/function activation/deactivation signal flows havebeen explained using call origination signaling, the signaling and MS101 user notification may also be achieved using Short Message Services(SMS) signaling with text messages or audio messages over a voicechannel. The audio notification can be accomplished by establishing avoice channel between the VAP 103 and the MS 101 and playing a recordedor voice synthesized message, e.g., Call forwarded to FwdDN to the MS101.

X. Call Hold [KAW-Completed Nov. 19, 1991]

Often, a telephone user, particularly a mobile phone user, ispreoccupied when an incoming call is received or is interrupted withsomething of a higher priority during an active call. For example, amobile telephone user may be in a meeting where the receipt of anincoming call would be a disruption. Thus, there is a need to allow auser to avoid disruption at particular times. However, the mobiletelephone user may wish for the call to be temporarily on hold becausethey will be available in a short period of time.

In existing wireless telephone handsets, a user can preset her wirelessphone so that an action is automatically taken when a call is received.For example, a user can preset a wireless telephone so that an incomingcall is forwarded to voice mail. While such systems allow a user toavoid disruption, they do not allow a user that may be available in theimmediate future, e.g., in a few seconds, to subsequently connect withthe call that has been directed to voicemail, i.e., to delay receipt ofthe call until the user is available. In the alternative, existingwireless telephone systems allow a user to place a call on hold duringan active call, for example, after answering an incoming call. However,answering the call immediately only to place the call on hold is alsodisruptive.

The call hold feature of the present invention enables existing wirelesshandsets to provide a user with the ability to interactively place anincoming call on hold in real time without first answering the call. Auser, who does not wish to be interrupted or needs to carry on a privateconversation off-line can either postpone answering an incoming callwithout first becoming involved in an active phone call conversation orby placing a presently active call on hold. According to one suchembodiment, the calling party can be coupled to, for example, a voiceprocessing unit (VPU) to receive a message that indicates the call is onhold and the called party (WCS subscriber) will be with them shortly.The WCS call hold feature allows the MS 101 user to reroute an incomingcall to the VPU without answering the incoming call even though theincoming call is in the process of being automatically routed to thevoice mail system (VMS). Thus, the WCS of the present invention providesa user with the ability to instantaneously place an incoming call onhold in real time or interrupt an incoming call routed to a VMS withoutfirst answering the call, have the caller automatically instructed thatthe call is on hold, and to pickup the call sometime in the near future.Therefore, the present invention allows a mobile phone subscriber toplace an incoming call on hold without first having to answer the callas well as allowing a mobile phone user to place an active call on hold.A detail discussion of the WCS call hold feature/function follows.

FIG. 12 shows an illustrative communications system in which the callhold feature of the present invention can be implemented. A publicswitched telephone network (PSTN) 125 is connected to a plurality ofcommunication networks, including one having a telephone 1215. The PSTN125 can be coupled to a plurality of local digital switches, such as(LDS) 104. As previously noted, the LDS 104 may be a TR-08 and/or GR-303compatible switch which employs distributed intelligence,process-oriented software, and coordinated autonomous computing elementsto provide a flexible, modular, reliable and robust digital switchingsystem. Exemplary, but not limiting, LDSs include the 5ESS manufacturedby Lucent Technologies and the DMS-100/500 manufactured by Nortel. TheLDS 104 can provide a single platform for advanced services includingISDN, Centrex, Custom Calling, and Advanced Intelligent Network (AIN)capabilities. The LDS 104 provides the switching fabric, administration,message switching and call switching functions.

The LDS 104 may be coupled to network server platform (NSP) 106 by anX.25 link 4 (packet switched data network link) and an SS7 link 5(signaling system for call setup and database transactions). The X.25link 4 carries call control messages on the D-channel between the NSP106 and LDS 104 that are destined for VAPs 103A and 103B. The SS7 link 5between the NSP 106 and LDS 104 carries the AIN (Advanced IntelligentNetwork) messages that directs the LDS 104 for proper routing of a callto a user who is a WCS subscriber.

NSP 106 may include, among other elements, a controller 1230, a voiceprocessing unit (VPU) 1235, memory 1240, and communications bus (CB)1238. The NSP 106 provides voice access ports (VAPs) 103A, 103B of thewireless centrex system with control and related operations,administration, maintenance, and provisioning (OAM&P) functions. Controlfunctions include, but are not restricted to, mobile station andmobility management, call control, and feature applications. The NSP 106is responsible for, among other functions, network intelligence for theVAP 103, validation, registration, and mobility management.

The LDS 104 may, for example, be connected to a RDT 102 by a Bellcorestandard GR-303 interface 1. The GR-303 standard defines digitaltransmission facility interfaces such as DS1 and SONET, concentrationoptions between the LDS 104/IDT 105 and the RDT 102, signaling options,and call processing and operations data links. The GR-303 interface 1can be transported across metallic (e.g., T1, ISDN: PR2 or DS3) orfiber-optic (e.g., SONET OC3 or OC12) links. The GR-303 interface 1carries the voice traffic and the signal traffic for the LDS 104 and theNSP 106.

The PSTN 125 may also be coupled to a mobile switching center (MSC)1250. The MSC 1250 generally has functionality similar to thecombination of LDS 104 and NSP 106, and operates to control a cellulartelephone network. Mobile switching center architectures are known inthe art, and it will be appreciated that any known MSC may be adaptedfor use with the present invention. Plural base stations are controlledby the MSC 1250, such as base station (BS) 1255. Mobile Stations (MS)can travel throughout the cellular network and within the WCS network.Depending on a number of factors, calls involving a mobile station arehandled by a base station that provides coverage for the area in whichthe mobile station is located. Handoff of calls involving the mobilestation from one base station to another is controlled by the MSC 1255in a known manner. A mobile station (MS) 101 is wirelessly coupled to BS1250 as shown.

On the other hand, when MS 101 enters the picocell area of a VAP in theWCS system, handsoff does not occur unless MS 101 has previousauthorization to operate within the WCS system. In fact, if the WCS isconstructed with security features/functions for restrictive access, theVAP 103 will deny registration and disconnect MS 101 from all macro andmicro cell base stations.

A more detailed representation of the elements of an illustrative WCSare depicted in FIGS. 1A-1C, and include, among other elements, the VAPn103A and 103B and two mobile communications units, e.g., IS-136 digitalTDMA cellular/PCS phones, MS 101A and 101B. Also shown are plain oldtelephone service (POTS) 108 and integrated services digital network(ISDN) 109.

Illustrative implementations of the functions for the call hold/unholdfeature of the present invention will now be described in connectionwith a wireless centrex system. However, it should be understood thatthe call hold/unhold feature service could also be supported in existingmacro cellular systems including an MSC and BS, if properly designed. Insuch a system, the MSC 1250 and BS 1255 would be programmed to be thefunctional equivalent of the WCS system including NSP 106 LDS 104, RDT102 and VAP 103 combined. However, it is noteworthy that the macrocellular system can not support ISDN and POTS wireline telephones butthe WCS system can because it is integrated into such existing systems.

FIG. 13 shows the call flow for setting up an incoming call (i.e., calltermination) similar to the call flow for setting up an incoming callillustrated in FIG. 5. For purposes of this discussion, it will beassumed that a calling party (e.g., telephone 1215) coupled to the PSTN125 (or connected to the same LDS) dials the phone number (DN) of themobile unit 101 and MS 101 is geographically within the WCS transmissionpicocell area.

The call with the DN arrives at the LDS 104 from the PSTN 125. The LDS104 receives the ISUP (integrated services digital network user part)IAM (initial address message) 508 message from the PSTN 125 (or a Q.931setup message). The LDS 104 determines whether the DN is provisioned forAIN termination attempt trigger (TAT), i.e., whether the DN isassociated with a WCS authorized MS. If so, the LDS 104 suspendsdelivery of the call and sends an AIN query message TCAP (AINTermination_Attempt [DN]) 509 to the NSP 106. The NSP 106 determineswhether the subscriber's mobile unit MS 101 is active and idle in itsserving area. If so, the NSP 106 pages the mobile unit MS 101 by sendinga Page Request [FDN, MSID] 510 message through the VAP 103 using IS-136established paging procedures, and starts the TT6-paging response timer.As part of the Page Request 510 message, the NSP 106 sends the VAP'sISDN forward directory number (FDN) and mobile station identificationnumber (MSID) that the VAP 103 uses to complete the incoming call setupprocedure.

The mobile unit MS 101 responds to the page by sending an IS-136 PageResponse 529 message to the VAP 103. The VAP 103 forwards the PageResponse message using Page Response 511, to the NSP 106 and startsevent timer TT5 to prevent permanent holding of RF and ISDN B-channelresources. When the NSP 106 receives the Page Response 511 message, itcancels the TT6 timer and knows that MS 101 is available to receive theincoming call and that the VAP 103 has the resources to support theincoming call. At the direction of the NSP 106, the LDS 104 forwards thecall to the FDN of the VAP 103 (e.g., in a TCAP conversation package)serving the mobile unit MS 101. The NSP 106 also indicates its interestin the event (O_No_Answer for FDN) by sending next event list (NEL)information to LDS 104 in a request component that accompanies therouting component in a conversation package (i.e., TCAP (AIN ForwardCall [FDN], NEL [O No Answer]) 512 message).

The LDS 104 starts a no answer timer (T(NoAnswer ) 531)) for the FDN andsends an ISDN Q.931 Setup [FDN] 513 message to the VAP 103. Upon receiptof the ISDN Q.931 Setup [FDN] 513 message, the VAP 103 cancels the TT5timer, invokes B-channel call processing, initiates an IS-136 digitaltraffic channel (DTC) designation to the mobile unit MS 101, starts theTT2 timer, and sends a ISDN Q.931 Call Proceeding 514 message to the LDS104.

The mobile unit MS 101 tunes to the designated DTC and sends anindication message, MS on DTC 515, to the VAP 103. When the VAP 103detects that the mobile unit MS 101 is on the requested traffic channelthrough a Digital Verification Color Code (DVCC; a layer 2 signal fromthe MS) status change, it cuts through the ISDN/B-channel and initiatesthe alerting procedures for each call leg, that is upstream to the LDS104 and downstream to the mobile unit MS 101. In particular, the VAP 103sends an IS-136 Alert-with-info 516 message to the mobile unit MS 101,starts the Alert timer (TT3), and sends an ISDN Q.931 Alerting 518message to the LDS 104. When the mobile unit MS 101 receives theAlert-with-info 516 message, it notifies the user through, for example,ringing (or an audible noise, vibrating, indicator lights, or a visualmessage display) that there is an incoming call (i.e., someone iscalling them). When the LDS 104 receives the ISDN Q.931 Alerting 518message, it sends an ISUP ACM (address complete message) 519 message toindicate that the Mobile Station MS 101 is available and communicatingwith the VAP and switches in the PSTN 125, and generates a ringback tone520 that is heard by the calling party.

The mobile unit MS 101 returns an alerting acknowledge, IS-136 Mobil ACK517, message to the VAP 103 so that the VAP 103 knows that MS 101 isalerting the user that there is an incoming call. Responsive to thealerting acknowledge message, the VAP 103 cancels the TT3 timer, startsa TT4 timer, and enters the wait-for-answer call processing state. Ifthe MS 101 user answers (accepts) the call by, for example, pushing asend (or talk) key on the mobile station, the mobile station MS 101sends an IS-136 Connect 521 message on the FACCH to the VAP 103. Inresponse, the VAP 103 cancels the TT4 timer and sends an ISDN Q.931Connect 522 message to LDS 104. After receiving the Connect message, theLDS 104 cancels the T(NoAnswer) 531 timer, and sends ISUP ANM (answermessage) 523 message to the switch in the PSTN 125 and cuts through thevoice path. Next, the LDS 104 sends an ISDN Q.931 Connect ACK 524acknowledge message to the VAP 103 and then sends a TCAP Completed 525message to the NSP 106 (using TCAP response) to complete the TCAPtransaction. After receiving the ISDN Q.931 connect ACK 524 acknowledgemessage, the VAP 103 sends a Termination Result [Success] 526 message(i.e., call connected) to the NSP 106 to indicate that the incoming callhas been successfully connected to the mobile station MS 101 and totrigger billing (air interface usage) and other OAM&P activities. Avoice path 527 is then established between the calling party and themobile unit MS 101. Once the call has been connected and a voice pathestablished the mobile station MS 101 user can place the active call onhold as described below.

If the MS 101 user does not answer the incoming call the T(NoAnswer)timer will expire and the incoming call will be handled according to themobile station MS 101 user's preprogrammed default designation. Forexample, the call could be forwarded to the VMS 107, the call could beforwarded to the MS 101 associated desk top phone 108, or the incomingcall may be allowed to continue alerting the mobile station (MS)indefinitely until the caller hangs up the telephone.

FIG. 14A shows the call flow for a first preferred embodimentillustrating implementation of the call hold/unhold feature performed onan active call. For purposes of this discussion, it will be assumed thatthere exists an active call between a mobile station MS 101 in a WCS anda calling party (e.g., using POTS telephone 1215) coupled to the PSTN125 and the call has been established either by a caller using POTS 1215initiating a call to MS 101 (i.e., as just described with reference toFIG. 13), or vice versa. In any case, an Active Call 1401 is in progressand the mobile station MA 101 user decides to place the active call onhold.

When the mobile user generates a hold command by, for example, pressinga hold button on their MS 101, an IS-136 call-hold request message 1402is sent over the FACCH (fast associated control channel) from the MS 101to the VAP 103 (with which the MS 101 is registered). The VAP 103interprets the request message, stops processing voice traffic frames,and notifies the NSP 106 that there is a call on hold 1404. Also, inresponse to the request message, the VAP 103 sends an IS-136 Call-HoldRequest Ack 1403 acknowledge message to the MS 101. The VAP 103continues to monitor the FACCH and also informs the NSP 106 that thecall is on hold (Call on hold 1404). In response the NSP 106 will send aCall on hold Ack 1405 message. If a personalized message has beenpre-recorded by the MS 101 user, the Call on hold Ack 1405 message willcontain the personalized message, i.e., the Call on hold Ack(personalized message) 1405 message will be provided from the NSP 106 tothe VAP 103.

When the VAP 103 places the call on hold, it may direct, for example,its own DSP (digital signal processor) to send a message and/or whitenoise (comfort noise such as music) 1406 to the calling party and/or theMS 101. The message and or white noise can be used to let the partiesknow that the call is still active and on hold. During the period thatwhite noise is sent to the MS 101, the MS 101 can continue to transmittraffic frames, but the VAP 103 will ignore the frames. Further, the VAP103 may also ignore voice traffic ransmitted from the calling party.

When the MS 101 user generates an unhold command by, for example,pressing the hold button again, the MS 101 transmits an IS-136Call-Unhold Request 1407 message on the FACCH to VAP 103. Upon receiptof the request message, the VAP 103 performs several actions. The VAP103 informs the NSP 106 that an active call has been resumed 1409 andalso instructs its DSP to stop generating white noise, if provided. TheVAP 103 again begins to process traffic frames (e.g., voice traffic)received from the MS 101 and sends the frames to the calling party andagain process voice traffic 1408 from the calling party directed to theMS 101. The VAP 103 also transmits a IS-136 Call-Unhold Request Ack 1408acknowledge message to the MS 101 to indicate that the call is resumed.

FIG. 14B shows the call flow for a second preferred embodimentillustrating implementation of the call hold/unhold feature performed onan active call. For simplicity, this signaling flow only discusses howthe system reacts to the feature when there is only one call for the MS101. For interactions with other features, e.g. Three-way Call, refer tothat section for more information.

First, the call is in progress, Call in progress 1420, and the MS userpresses, for example, the send button on MS 101. An IS-136 Flash WithInfo 1421 message is sent to the VAP 103. The VAP 103 sends an IS-136Flash With Info ACK 1423 message to the MS 101 and sends a FeatureRequest [FlashWithInfo] 1422 message to the NSP 106 which indicates thatthe MS 101 user is initiating a call hold. When the NSP 106 receives theFeature Request [FlashWithInfo] 1422 message from the VAP 103, itanalyses the message and confirms that the mobile is not involved in a3-way call. If the current call reference indicates that this is athree-way call, the Flash-With-Info message received by the NSP will beexamined with different set of rules similar to those described in thesection herein related to conference calling. The NSP 106 theninterprets the message as a request for Call Hold and validates that theMS 101 is authorized to the Call Hold feature. If the validation issuccessful, the NSP 106 sends a Feature request ACK [Call Hold] 1424message to the VAP 103, the action field being designated as Call Hold.If the MS 101 is not authorized to use Call Hold feature, the NSP 106ignores the Feature Request [FlashWithInfo] 1422 message. Further, theNSP 106 may, but not need, send a Feature Request NACK message to theVAP 103 because the VAP 103 has no action to take upon such a message.It may play a voice prompt or send a short message to the user in such acase for future releases of the feature.

Next, the VAP 103 sends Q.932 Hold 1425 message to the LDS 104 andstarts a THh timer. In response, the LDS 104 sends a Q.932 Hold ACK 1426message to the VAP 103 and the VAP 103 stops the THh timer. The call isplaced on hold with the LDS 104, Call held 1427. However, if the VAP 103receives a Q.932 Hold NACK message from the god LDS 104 it will send outa Call Held [Fail] message to the NSP 106. Further, if the timer THhexpires, the VAP 103 will log an error and send out a Call Held [Fail]message to the NSP 106.

Next, the VAP 103 sends a Call Held [success] 1428 message to the NSP106, and if provisioned, plays a voice prompt to inform the user thatthe call is on hold and/or music (VAP plays voice and/or music 1429),and starts TH1 timer. However, if the NSP 106 gets a Call Held [fail]message form the VAP 103, it will modify the call information record (ifneeded) and the call will remain in a ‘talk’ state.

When the MS 101 user wants to retrieve the call it presses, for example,the send key or the hold key again on the MS 101 and IS-136 Flash withInfo 1430 message is sent to the VAP 103. When the VAP 103 receives theIS-136 Flash with Info 1430 message, the VAP will look at theappropriate record to find that this message has come for a call whichis currently on hold. The VAP 103 stops the TH1 timer and sends back anIS-136 Flash With Info Ack 1431 message to the MS 101. Since the VAP 103has determined that this is a request to retrieve the held call, itsends a Q.932 Retrieve 1432 message to the LDS 104 and starts the TRrtimer. However, if the TH1 timer expires, the VAP 103 shall play a voiceprompt (optional) to the user informing him that the call is beingdisconnected. It shall then follow, for example, the VAP 103 OA&MRelease procedure and release the call.

When the VAP 103 receives a Q.932 Retrieve ACK 1433 message from the LDS104, it cancels the TRr timer and sends a proprietary Call Retrieve[success] 1434 message to the NSP 106. However, if the VAP 103 receivesa Q.932 Retrieve NACK message from the LDS 104, it will send out a CallRetrieved [Fail] message to the NSP 106. Further, if the timer TRrexpires, the VAP 103 will log an error, send out a Call Retrieved [Fail]message to the NSP 106 and initiate, for example, a VAP 103 OA&M Releaseprocedure.

Then, the NSP 106 modifies the call record information to indicate thata call is in progress with MS 101. If the NSP 106 receives a CallRetrieved [fail] message from the VAP 103, it shall stop the TH2 timerand update its call information record. Further, if the timer TH2expires, the NSP 106 will initiate, for example, an OA&M Releaseprocedure. Finally, the call is retrieved and resumes as Call inprogress 1435.

As indicated above, another embodiment of the call hold feature/functionmay include the use of a personalized message to be used prior to, or inplace of, a system default voice prompt and comfort noise (e.g., music)when a call is placed on hold. The MS 101 user may use the VPU 1235 torecord personalized messages for the call hold feature/function. If theMS 101 user enters a special feature access code, for example *70, toinitiate recording a personalized message recording in the VPU 1235. TheNSP 106 validates the MS 101 and assigns call resources to the MS 101.Then the VPU 1235 prompts the user to record their personalizedgreeting. Once the greeting is completed, the NSP 106 stores it in, forexample memory 1240, for the MS 101 user in their subscriber profile.Next, the NSP 106 frees the call resources. If the user wishes to modifyor delete their personalized greeting they may enter another featurecode, for example *71.

When the user is on an active call and invokes the call holdfeature/function, a message is sent by the VAP 103 to the NSP 106indicating invocation of the feature. In response, the NSP 106 checksagainst the subscriber DB stored in, for example memory 1240, todetermine if there is a personalized greeting available for the MS 101user that may be used for a call hold. If there is a personalizedgreeting for the MS 101 user, the NSP 106 sends it to the VAP 103 andmay be included as part of a call hold acknowledgement message. When theVAP 103 receives the call hold acknowledgement message, if there is apersonalized greeting for MS 101, it will play that to the calling partyof PSTN 125/1215. If there is no personalized greeting for the MS 101user, the NSP 106 may send a call hold acknowledgement message withoutany personalized message and the VAP 103 will play some other defaultmessage, for example, a system default generic message indicating thatthe call has been placed on hold. In either case, the VAP 103 maysubsequently play comfort noise, e.g. music to the calling party placedon hold. Alternatively, the VAP 103 may play the comfort noise to bothparties without any prior message. Although this personalized greetingfeature is described with respect to call hold, it may also be used inconjunction with call screen and distinctive ringing feature/functionsas well.

FIG. 15 shows the call flow for an illustrative implementation of thecall hold/unhold feature for an unanswered incoming call. As with FIG.13, it will be assumed that a calling party (e.g., telephone 1215)coupled to the PSTN 125 (or at the same LDS) dials the phone number (DN)of the mobile unit MS 101 and MS 101 is within the transmission servicepicocell area of the WCS.

When the mobile unit MS 101 receives an incoming call, the mobile unitMS 101 can alert the user of the incoming call by, for example, ringingor other audible noise or alerting methods. Also, caller ID informationcan be provided that shows up on a display of the mobile unit MS 101.FIGS. 5 and 13, as discussed above, shows the call flow for delivery ofand answering of an incoming call. However, rather than answer theincoming call the mobile station MS 101 user can decide to place theincoming call on hold before answering it (i.e., before pressing, forexample, a send key (e.g., talk, on, yes, answer, etc.) on MS 101 andinitiating a personal conversation with the caller). Rather than answerthe call immediately, the mobile station MS 101 user can accept the callwithout answering it by first putting the incoming call on hold asdescribed below.

Upon being alerted of the incoming call, a user 1520, not wishing toanswer the call immediately, can generate a hold command by, forexample, pressing a hold button on the mobile unit MS 101 or entering afeature code (e.g., *95). When the user inputs a hold command, the callis accepted (i.e., connected) and put on hold rather than being answeredand a voice path being cut to the mobile station MS 101. However, whenthe call is accepted, resources including a traffic (e.g., voice)channel are allocated for the call and white noise or an announcementwill be provided. Also, the call is connected in the same manner asdescribed above and shown in FIGS. 5 and 14 illustrated as step 1506.

The VAP 103 receives a call hold request via an IS-136 Call-Hold Request1505 message from the mobile unit MS 101 and sends, for example apersonalized message or a default message, e.g., a generic system callon hold announcement to the calling party (Call on hold announcement tooriginating party on DTC 1508). The VAP 103 also sends an IS-136 CallHold Request ACK 1507 acknowledge message to the mobile unit MS 101 andnotifies the NSP 106 that the mobile unit MS 101 has put the call onhold (call on hold 1510). Thus, the call is placed on hold with the VAP103 and the VAP notifies the NSP 106 using the Call on hold 1509message.

A DSP in, for example, the VAP 103 may send a message or comfort noise(i.e., white noise such as music) to the user of the mobile unit MS 101and to the calling party while the incoming call is on hold. In thealternative, the VPU 1235 may play a short message (announcement) sentto the VAP 103 via a call on hold Ack message indicating the call is onhold prior to the DSP sending a system default message or comfort noise.While the call is on hold, the mobile unit MS 101 can continue totransmit traffic frames, but the VAP 103 will ignore the frames.Further, the VAP 103 may ignore voice traffic transmitted from thecalling party (e.g., mute).

When the user of the mobile unit MS 101 desires to retrieve the heldcall, the user can generate an unhold command by, for example, pressingthe hold button (or feature code) again 1511 on the mobile unit MS 101.In response, to a call unhold command, the mobile unit MS 101 sends anIS-136 Call-Unhold Request 1512 message on the FACCH to the VAP 103. TheVAP 103 interprets this message and directs the DSP to stop sendingwhite noise, if provided. In response to message, the VAP 103 begins toprocess traffic frames received from the mobile unit MS 101 and sendsthe same to the calling party. The VAP 103 sends a notification to theNSP 106 that the call is no longer on hold and has become active (callresumed 1514). Also, the VAP 103 begins processing the voice trafficfrom the calling party transmitted to the mobile unit MS 101, thusestablishing an Active Voice Call 1515.

According to another illustrative embodiment of the present invention,the call hold button can act similar to a call mute button when a callis placed on hold, by for example pressing the hold button twicequickly. In this implementation, the mobile unit MS 101 can receivevoice traffic from the calling party, while the calling party is mutedfrom any voice traffic generated by the called party. In this instance,the calling party may receive white comfort noise when on hold. Thiscall muting type functionality creates one way voice traffictransmission. Such an implementation may be beneficial in allowing thecalling party to communicate a brief message to the called party at anytime after the call has been placed on hold. Thus, if a calling partyhas an emergency message or an important message that cannot wait, thecalled party may receive this message in real time.

In one embodiment a call hold announcement may be played to the calledparty or an alert is provided to the called party to remind them thatthe a call is on hold. During the announcement to the called party theone-way communication line can be temporarily shut off or optionallyopen for voice traffic. As previously noted, a call hold announcementmay also be sent to the calling party. The call hold announcement may berepeated to the calling party and/or the called party at predefinedintervals (e.g., every 30 seconds) subsequent to initiation of the callhold.

Furthermore, in another embodiment, the call hold feature may allow acalling party to interactively transfer to a voice mail system or sendan alphanumeric message to the called party rather than simply wait onhold. For example, when a call is on hold the VPU 1235 can notify thecalling party the they may leave a message in the called party voicemail by entering a particular set of key strokes (e.g., *34#) or enterany alphanumeric message using their telephone key pad. The NSP 106 willrespond to the input by the calling party and instruct the LDS 104 toroute the input accordingly to either the VMS 107 or the MS 101. A moredetailed discussion of the announcement features and additional featuresrelated to user proactive call handling follows.

XI. User Proactive Call Handling

Another feature of the present invention provides user proactive callhandling (UPCH) functionality. This feature allows a mobile telephoneuser to proactively handle a call in an intelligent wirelesscommunications system. One aspect of this feature allows a user toprocess and terminate an incoming call in real time. Another aspect ofthe UPCH feature provides the ability to delay allocation of the voicechannel to a called party until when, if at all, the incoming call tothe called requires a voice channel.

According to an illustrative embodiment of the present invention, asubscriber is notified of an incoming call via a Short Message Service(SMS) message with caller ID or a user alert, such as a tone or ringing.Upon receipt of the alert, the subscriber may select from a series ofoptions, how to process and terminate the incoming call. For example, ifan incoming call is of high priority and requires immediate attention,the subscriber may decide to answer the call immediately. If thesubscriber decides that the call does not require immediate attention,he may opt to provide a delayed answer. Such a delayed answer option caninvolve connecting the call to an announcement prior to answering thecall. Still further, if neither of the prior options is suitable, thenthe subscriber may opt to send the call to a voice mail system, fromwhich a recorded message can later be retrieved. Yet another option ofterminating the call is to forward the call to another phone. In theevent that the subscriber decides that the incoming call should not beanswered, the subscriber may choose to reject the call. If thesubscriber decides that none of the aforementioned options should beproactively taken, then a default option can be used to terminate thecall. Such a default option may include, but is not limited to,forwarding the call, delaying the answer, sending the call to a voicemailbox, or rejecting the call. A detailed discussion of the systems andmethods for implementing UPCH features/functions in a WCS follows.

The UPCH feature, like the call hold feature of the present invention,can be implemented using the illustrative communications system of FIG.12. A public switched telephone network (PSTN) 125 is connected toplural communication networks, including one having a telephone 1215.The PSTN 125 can be coupled to a plurality of local digital switches,such as local digital switch (LDS) 104. The LDS 104 may be coupled tonetwork server platform (NSP) 106 by an X.25 link 4 and an SS7 link 5.NSP 106 may include, among other elements, a controller 1230, a voiceprocessing unit (VPU) 1235, memory 1240, and communications bus (CB)1238. The NSP 106 provides voice access ports (VAPs) 103A, 103B of awireless centrex system with control and related operations,administration, maintenance, and provisioning (OAM&P) functions. Controlfunctions include, but are not restricted to, mobile station andmobility management, call control, and feature applications. The NSP 106is responsible for, among other functions, network intelligence,validation, registration, mobility management, and serves as a messagecenter.

The X.25 link 4 carries call control messages on the data channel(D-channel) between the NSP 106 and LDS 104 that are destined for theVAPs 103A and 103B. The SS7 link 5 between the NSP 106 and LDS 104carries the AIN (Advanced Intelligent Network) messages that direct theLDS 104 for proper routing of call to a user who subscribes to wirelesscentrex system (WCS) services.

The LDS 104 may be connected to a remote digital terminal (RDT) 102 by aBellcore standard GR-303 interface 1. The GR-303 standard definesdigital transmission facility interface such as DS1 and/or SONET,concentration options between the integrated digital terminal (switch)105 and the RDT 102 signaling options, and call processing andoperations data links. Thus, the GR-303 interface 1 can be transportedacross metallic (e.g., T1, ISDN:PR1 or DS3) or fiber-optic (e.g., SONETOC3 or OC12) links. The GR-303 interface carries the voice traffic andthe signal traffic for the LDS 104 and the NSP 106.

The PSTN 125 is also coupled to a mobile switching center (MSC) 1250.The MSC 1250 has functionality similar to the combination of LDS 104 andNSP 106, and operates to control a cellular telephone network. MSCarchitectures are known in the art, and it will be appreciated that anyMSC may be adapted for use with the present invention. Plural basestations (BS), for example like the one BS 1255, are controlled by theMSC 1250. Mobile stations MS 101 can travel throughout the cellularnetwork and into the WCS network. Depending on a number of factors,calls involving a mobile station are handled by a base station BS 1255that provides cellular coverage for the area in which the mobile stationis located. Handoff of calls involving the mobile station MS 101 fromone base station BS 1255 to another base station BS 1255 is controlledby the MSC 1250 in a known manner. A mobile station MS 101 may bewirelessly coupled to BS 1255 as shown or alternatively to a VAP 103 forcommunication connection to other telephones within the entire PSTN,cellular telephone, and WCS configuration. Thus, the WCS can connect toa macro cellular SS7 network to support integrated mobility functionsincluding terminal handoff and personal roaming features.

On the other hand, as illustrated in FIG. 1, a WCS can operate as awireless system without being connected to a public macro cellularsystem, and thus not support mobility functions associated with themacro cellular system.

An illustrative implementation of the UPCH service of the presentinvention will be described in connection with a wireless centrexsystem. However, it should be understood to those skilled in the artthat the UPCH service can also be supported in existing macro cellularsystems. In such a system, the MSC 1250 can provide similarfunctionality to the NSP 106 plus the LDS 104, and a BS 1255 isfunctionally similar to a VAP 103.

FIG. 16 provides an exemplary call flow diagram for activating the UPCHfeature according to an illustrative embodiment of the presentinvention. To activate the UPCH service, a subscriber enters an FeatureActivation Code (FAC) 1601 (e.g., *1) on his mobile station MS 101 andpresses, for example, a SEND button or some other designated key stroke.An IS-136: Call Origination<FAC> 1602 message is sent to, for example,VAP 103A which forwards the message upstream through the RDT 102 and LDS104 (not shown) to the controller 1230 of the NSP 106 as CallOrigination <FAC> 1603 message. The controller 1230 updates informationfor the subscriber in memory 1240 that includes a database, and sets theUPCH service feature active for the subscriber at step 1604.

The controller 1230 of the NSP 106 then sends UPCH FAC ACK 1605acknowledgment message back to the subscriber's mobile station MS 101Athrough the LDS 104, RDT 102 (not shown) and VAP 103A (UPCH FAC 1606).After the acknowledgement signal has been received a character on themobile station MS 101A, for example on a display screen, may beilluminated to indicate that the UPCH service is active.

The database in memory 1240 may contain, among other things, a profilefor each subscriber including services available to the subscriber andpreferences of the subscribers which can be dynamically changed by asubscriber telephonically, over the Internet, or otherwise.

If a subscriber desires to deactivate the UPCH feature, the subscribercan enter a feature deactivation code FDC (e.g., the AFC code plus *3)and press, for example, the SEND button on his mobile station MS 101 asshown in step 1607. An IS-136 Call Origination <FAC*3> 1608 messagehaving the feature deactivation code is then sent upstream to thecontroller 1230 of the NSP 106 by way of, for example, the VAP 103, RDT102, (not shown) and LDS 104 (Call Origination <FAC> 1609). Thecontroller 1230 of the NSP 106 updates the subscriber's profile inmemory 1240 by setting a UPCH feature flag inactive. The controller 1230of the NSP 106 may then send an acknowledgment message, UPCH FDC ACK1611, back to the subscriber's mobile station MS 101A through, forexample, the LDS 104, RDT 102 (not shown) and VAP 103A (UPCH FDC ACK1612). After the acknowledgement signal has been received by the MS 101,an UPCH indicator on the mobile station MS 101A may be turned off toindicate that the UPCH service is inactive.

Another illustrative implementation of the UPCH service feature will nowbe described in connection with call flow diagram of FIG. 17. Anincoming call 1701 to a mobile station MS 101A is delivered to thecontroller 1230 of the NSP 106. The incoming call 1701 can originateanywhere in the communications network including from a caller in acellular system (e.g., MS 101), wireless centrex system (e.g., mobilestation MS 101B), the PSTN 125 (e.g., landline phone 1215), or any localand long distance network.

The controller 1230 retrieves profile information 1702 associated withthe called party from the memory 1240. If the UPCH active flag is setfor the called party, the controller 1230 can send a short message (SM)<Reason, Caller ID> 1703 to the VAP 103A with which the called partymobile station MS 101A has registered. The SM transmitted to the calledparty indicates that an incoming call exists and may further includecaller ID data such as the calling party's name and/or number.

The short message may be transmitted to the called party in a portion ofthe DCCH known as a short message service channel (SMSCH). An exemplaryimplementation of the short message is described in the IS-136 EIA/TIAInterim Standard. The SMSCH can carry signal information for set up anddelivery of short alphanumeric messages from the NSP 106 to the mobilestation 101A of the called party. The SMSCH is a logical sub-channel ofthe SMS point-to-point messaging, paging, and access response channel(SPACH), which is a logical channel of the DCCH. The DCCH operates on aset of frequencies separate from those used to support cellularconversations, which may be carried on the DTC.

After the SM 1703 is received by the VAP 103A at which the calledparty's mobile station MS 101A is registered, according to thisillustrative embodiment, the VAP 103A follows the IS-136 specificationby first sending a SPACH Notification 1704 message to the called party'smobile station MS 101A. The mobile station MS 101A sends a SPACHConfirmation 1705 acknowledgement message to VAP 103A and then the VAP103A sends RDATA 1706 message including the short message SM to themobile station. Thereafter, the mobile station MS 101A acknowledgesreceipt of RDATA by sending RDATA Accept 1707 message back to the VAP103A.

When the short message is delivered to the called party, it is displayedon the called party's mobile station MS IOIA. Thus, the called partyknows that an incoming call exists and the identity of the callerthrough the caller ID information displayed on the called party's mobilestation. The called party then can decide how to handle the incomingcall. Options available to the subscriber may include: a) answer thecall immediately; b) delay answering the call; c) immediately forwardthe call to voice mail; d) forward the call to another number; e) rejectthe call; f) send a short message to the calling party; and g) take noaction. The calling party can select an option by, for example, pressingone or more keys on the mobile station keypad of pressing a touchscreen. A discussion of the operation of some of the possible mobilestation MS 101 user UPCH selections follows.

According to a first aspect of the UPCH feature implementation, when thecalled party desires to answer the incoming call immediately hedepresses a button or key (e.g., TALK or SEND) at the mobile station MS101A. A call origination message is then transmitted upstream in theDCCH to the VAP 103A and up to the LDS 104 and NSP 106. The NSP 106immediately allocates a voice channel between the LDS 104 and the mobilestation 101A that connects with the voice path previously establishedbetween the calling party and LDS 104 when the calling party firstinitiated the call, to thus establish a point-to-point voice channelbetween the calling and called party. High priority may be given to thecalled party's request for a voice path e.g., a DTC channel may bequickly allocated.

According to a second aspect of the UPCH feature, a MS 101 user maychose to delay answer of a call and would enter a different functioncode, for example, pressing “*1, Send”. This key stroke would forwardthe incoming call to an announcement stored in the voice processing unit(VPU) 1235 of the NSP 106. FIG. 18 shows an exemplary call flow diagramfor the delay answer call option in accordance with an illustrativeembodiment of this aspect of the present invention.

First, an incoming call is provided with a voice path 1801 between thecalling party and LDS 106. The LDS 106 passes the incoming call 1701including a route query to the controller 1230 of the NSP 106. Thecontroller 1230 retrieves the profile of the called party from memory1240. If the UPCH service is active for the called party, a shortmessage SM <Reason, Caller ID> 1703 is sent to the mobile station MS101. As described above and shown in FIG. 17, steps 1704-1707 followsand the user is provided an opportunity to determine in real time how tohandle the incoming call.

The called party receives the message and decides that he wants toanswer this call after some delay. So the called party enters a delayanswer feature code such as “*1 SEND” 1808 and an IS-136: CallOrigination 1809 message, with “*1” as the keyed input, is sent upstreamto the NSP 106 by way of VAP 103A (Call Origination 1810). Thecontroller 1230 receives the message, updates the called party'sdatabase in memory 1240 with current status information, and instructsthe LDS 104 using Reroute to VPU 1811 to connect the calling party'svoice path to the VPU 1235. The VPU 1235 plays a brief message, such as“Please wait, [the called party name] will be with you shortly” in step1812 and places the call on hold (with or without white noise generatedby a DSP).

When the called party subsequently becomes available and desires to beconnected with the on hold calling party, he enters a key feature codesuch as “*7 SEND” in step 1813. An IS-136: Call Origination <FC*7> 1814message, with “*7” as the feature code, is sent to VAP 103A whichforwards the Call Origination 1815 message to NSP 106. The controller1230 of the NSP 106 receives the message, updates the status of thecalled party in memory 1240, and retrieves the active call information.If the calling party is still holding, the controller 1230 instructs theVAP 103A to barge into the voice path established between the callingparty and VPU 1235 (or DSP), establishing a three-way connection. Then,the controller 1230 instructs the VPU 1235 (or DSP) to disconnect fromthe voice path using Call Disconnect 1818 message, leaving the calledparty and calling party on the voice path. If the calling party is noton hold, the NSP 106 can instruct the VAP 103A to dial the last incomingcall in the called party's record in memory 1240.

According to another aspect of the UPCH feature, a mobile station usercan in real time forward an unanswered incoming call to voice mail byentering a function code, for example by pressing “*2, SEND”. In thisinstance, an origination message with “*2” is sent upstream in the DCCHto the LDS 104. The LDS 104 then routs the call to a VMS 107 coupled tothe LDS 104, where the calling party can leave a voice message.

Similarly, according to a further aspect of the UPCH feature, a mobilestation user can in real time forward an unanswered incoming call toanother DN or extension by entering a function code, for example bypressing “*3, and [the number of the forwarding location], SEND”. The idnumber of the forwarding location is transmitted upstream to the LDS 104and NSP 106 which examines the id number to which the call is to beforwarded. If the id number matches a number in the system associatedwith LDS 104 or LDS 104A, etc., the call is processed accordingly.Otherwise, the call is routed through, for example, the PSTN 125 to theappropriate end DN to receive the call.

According to another aspect of the UPCH feature, a mobile station usercan in real time reject an unanswered incoming call by entering afunction code representing a rejection key sequence, for example, “*4SEND”. In response an origination message with “*4” is sent upstream tothe LDS 104 and NSP 106 in the DCCH. A message indicating that thecalled party is not currently accepting calls may be issued by, forexample, VPU 1235, to advise the calling party. Alternatively, a tonemay be transmitted from the LDS 104 to the calling party when the LDS104 and/or NSP 106 detect a call reject flag.

According to still another aspect of the UPCH feature, a mobile stationuser can in real time create a short message and send it to the callingparty of an unanswered incoming call by the called party entering afunction code along with a message, for example, “*6, [a briefalphanumeric or voice message], SEND”. The short message travelsupstream in the DCCH to the LDS 104 and NSP 106, where it is transmitteddownstream to the calling party. Voice synthesis in the VPU 1235 or DSPin the VAP 103 may be used to convert the alphanumeric message to avoice message. This feature may be particularly advantageous when thecalled party is busy and simply wants to communicate a brief real timemessage such as “Call you back in ten minutes” or “Meet me at home at6:00”.

According to a further aspect of the UPCH feature, the called party canalso chose to take no affirmative action so that a default action isimplemented after a prescribed time period in the which the called partyhas failed to respond lapses. Default conditions may include, but arenot limited to, forwarding the call to voice mail or letting the call gounanswered. The default condition for a particular subscriber is definedin the subscriber profile stored in memory 1240 of the NSP 106. Thus, ifthe NSP 106 fails to receive any response from a called party, the NSP106 will automatically process and terminate the call according to thecalled party's profile.

The UPCH service of the present invention can be integrated with anautomatic call handling service, where based on certain criteria, a callcan be handled automatically, and based on other criteria, a call canhandled by the UPCH service. For example, a user may want all callsforwarded to voice mail from 10:00PM to 8:00AM and from 8:00AM to10:00PM desire to process and terminate calls proactively. Also, a usermay want all calls originating from certain IDs to be handledautomatically while the remainder of the calls can be processed andterminated proactively. Further, a called party may desire to processand terminate calls proactively based on the physical location of thecalled party (e.g., office v. home). All this information can be definedand programmed in the called party's profile in the memory 1240 so thatthe NSP 106 knows how to route an incoming call properly according to auser's predefined or system default preference settings.

According to another illustrative embodiment of the invention, the NSP106 can transmit a user alert, such as a tone, over the control channelto the called party to apprise the called party of an incoming call. Auser alert can be incorporated with or without the SM application ofUPCH described above. In response to the user alert, the called partycan process and terminate the incoming call in real time as describedabove. Different tones can be assigned in the called party's profile inthe memory 1240 so as to uniquely or specifically identify the callingparty.

Further, the UPCH feature provides the ability to delay allocation ofthe voice channel to a called party until when, if at all, the incomingcall to the called party requires a voice channel. This is carried outby allowing a called party to receive notification of an incoming callover the control channel and to return the selection of the callhandling options upstream over the control channel. Thus, a voicechannel need not be allocated until the called party decides to answerthe call. This can be beneficial in wireless environments to prevent theunnecessary allocation of voice channels. Once the called party needs avoice channel, the incoming call has priority for available voicechannels.

XII. Call Transfers

From time to time a telephone user, particularly a mobile phone MS 101user, has need to transfer an active call to another telephone DN. Suchsituation arise when the other party needs to talk with someone else orwould like to access a voice mail message in, for example, a VMS. Insuch instances the mobile station MS 101 user needs a quick, userfriendly means to transfer the active call to another DN, i.e., thetransfer-to DN (TransferDN).

The call transfer feature/function allows the WCS MS 101 user totransfer an active call to another DN. The transfer-to DN can be eitherinside or outside the WCS network.

The two exemplary embodiments provided below illustrate the calltransfer feature/function where an active call is transferred from a WCSmobile station (e.g., MS 101A) to another mobile station (e.g., MS 101B)or to a PSTN telephone (e.g., PSTN 1215), respectively.

Referring to FIG. 19, a first preferred embodiment for the call transferfeature/function shows a call transferred by a mobile station MS 101user from mobile station MS 101 to PSTN DN2 (1215 b) outside the WCS.Initially, it is assumed that a call between MS 101 and PSTN DN1 is inprogress and the LDS 104 and VAP 103 identify this existing call as callreference 1 (Call in progress, CR=1 1900 shown as dashed lines at thetop of FIG. 19). The MS 101 user may transfer an active call by enteringa feature/function code for call transfer and digits associated with theDN to which the call is to be transferred. For example, the MS 101 usermay enter on the MS 101 keypad the digits in the format of, for example,*77#TransferDN (the transfer-to DN is denoted as the TransferDN) and the“send” button. Each time a digit is pressed on the MS 101 a IS-136 SendBurst DTMF message is sent to the VAP 103 which in total is representedby the IS-136 Send Burst DTMF [*77#TransferDN] 1901 message,corresponding to all of the digits pressed. Then, by the MS 101userpressing the “send” button, the MS 101 sends an IS-136 Flash WithInfo message to the VAP 103 indicating that the previously sent IS-136Send Burst DTMF messages are complete and represent the end of thetransmission representing a call transfer request.

Upon receiving each DTMF message from MS 101, the VAP 103 sends anIS-136 Send Burst DTMF ACK 1902 message to the MS 101. After receivingthe Flash With Info 1903 message from MS 101, VAP 103 sends a uniqueFeature Request message including the collected digits to the NSP 106,e.g., Feature Request [*77#TransferDN] 1904 message.

When the NSP 106 receives the Feature Request [*77#TransferDN] 1904message it identifies that the digits *77# is the feature code for theCall Transfer feature. Then the NSP 106 analyzes the feature code digitsand validates via the WCSD in, for example, memory 1240, whether MS 101is authorized for the feature requested. If MS 101 is authorized to usethe call transfer feature requested, the validation is successful andNSP 106 sends a Feature Request ACK [Play Voice Prompt (Transfer)] 1906message to VAP 103 with the action as ‘Play Voice Prompt’ instructingVAP 103 to play an announcement/tone to the MS 101 user (and/or the PSTNDN1 1215 b) indicating that a call transfer has been authorized (VoicePrompt 1907). Similar to the Call Hold feature/function procedure, theMS 101 and the PSTN DN1 1215 b may be provided comfort noise by adigital signal process (DSP) to maintain continuity. However, if thevalidation of the Call Transfer feature/function request at NSP 106 isunsuccessful, the NSP 106 sends a Feature Request NACK (NotAcknowledged) message to VAP 103 prompting it to play an appropriateannouncement/tone to the MS 101 indicating that the call transferfeature/function is not available and the call will not be transferredto the requested transfer-to DN (e.g., a Feature Request NACK [PlayVoice Prompt (Transfer Not Allowed)] message is sent to VAP 103).

Once the call transfer has been authorized and the NSP 106 has sent aFeature Request ACK message to VAP 103, the NSP 106 sends a uniqueTransfer message, Transfer [CR=1, TransferDN] 1908, to the VAP 103including the MSID of the requesting mobile station MS 101, the VAP IDto which the message is directed, the call reference number (e.g., CR=1)and the transfer-to DN, TransferDN, to execute the call transferprocedure. The NSP 106 also starts the TCT2 timer to ensure that theactive call will not stay on hold indefinitely if for some reason thecall is not properly transferred to the transfer-to DN.

In response to the Transfer [CR=1, TransferDN] 1908 message, the VAP 103sends an information message, Q.931 Info [CR=1, Transfer] 1909, to LDS104 to request the call transfer for the current call (CR=1). In return,the LDS 104 sends a Q.932 Hold [CR=1] 1910 message to the VAP 103. ThenVAP 103 places the call on hold and sends a Q.932 Hold ACK [CR=1] 1911message back to the LDS 104. VAP 103 also sends a Q.931 Setup [CR=2,TransferDN] 1913 message having the call reference CR=2 and thetransfer-to TransferDN to the LDS 104. The LDS 104 initiates the ISUPconnection to the TransferDN (PSTN DN2 1215 a in the figure), and VAP103 waits with the call on hold for the Q.931 Connect [CR=2] 1920message from LDS 104.

In establishing the call initiation with PSTN DN2 1215 a, PSTN DN2 1215a (i.e., PSTN switch which services DN2) receives an ISUP LAM 1914message from LDS 104 and VAP 103 receives a Q.931 Call Proceeding 1915message from LDS 104. In response, PSTN DN2 1215 a send an ISUP ACM 1916message to LDS 104 and LDS 104 provides a Q.931 Alerting 1917 message toVAP 103. A Ringback Tone 1918 is provided to MS 101 so that the MS 101user understand that the TransferDN is being alarmed as an incomingcall. When PSTN DN2 1215 a answers the call, an ISUP ANM 1919 message issent to LDS 104. The LDS 104 recognizes that the incoming call has beenanswered by the PSTN DN2 and sends the Q.931 Connect [CR=2] 1920 messageto VAP 103.

However, the MS 101 user can interrupt the call transfer before thecalled party at PSTN DN2 1212 a answers (i.e., before the call istransferred), by for example pressing the send button on the MS 101twice. In a situation when the MS 101 user is getting a busy signal orPSTN DN2 1215 a is still ringing and the MS user presses the send buttononce, the message generated from the MS 101 will be ignored by the NSP106. However, if the MS 101 user presses the send button twice within ashort period of time (e.g., a one-second period) and the call has notyet been answered by the PSTN DN2 1215 a (the ISUP ANM 1919 message andQ.931 Connect [CR=2] 1920 message have not been generated), the NSP 106identifies that the MS 101 is requesting to retrieve the held call andterminate the call transfer. Thus, in response the system will retrievethe original call (CR=1) and release the second call (CR=2).

Assuming that the MS 101 user does not interrupt the call transfer andthe PSTN DN2 1212 a answers, the PSTN DN2 1215 a sends the ISUP ANM 1919message to LDS 104 and the LDS 104 sends the Q.931 Connect [CR=2] 1920message to the VAP 103. When the VAP receives the Q.931 Connect [CR=2]1920 message from the LDS 104, it acknowledges connection with the PSTNDN2 and sends a Q.931 Connect ACK 1921 message back to LDS 104 and sendsa Transfer Result [TransferDN, Answered] 1922 message to NSP 106informing the NSP 106 that the TransferDN has answered. The uniqueTransfer Result message includes the MSID, VAP ID, Call Reference Number(e.g., CR=2), and Cause (e.g., success/fail).

When the NSP 106 receives the unique Transfer Result [Transfer DNAnswered] 1922 message from VAP 103 informing that the TransferDN hasanswered, the NSP 106 updates the call transfer status and cancels theTCT2 timer. If the timer TCT2 expires before receiving the TransferResult 1922 message, the NSP 106 shall deactivate the Call Transferfeature by sending a Feature Request NACK message (not shown) inresponse to the Feature Request from VAP 103. Then the VAP 103 shallsend a Q.932 Retrieve [CR=1] message (not shown) to the LDS 104, whichretrieves the held call [CR=1] and sends a Q.932 Retrieve ACK back tothe VAP 103.

In the case that the Transfer Result [Transfer DN Answered] 1922 messageis received by NSP 106 with the Transfer DN Answered message, if the MS101 user now presses, for example, the “send” button once, an IS-136Flash with Info 1923 message is sent to the VAP 103 to initiatecompletion of the call transfer (connecting call CR=1 from the PSTN DN11215 b to the LDS 104 to the call CR=2 from the LDS 104 to the PSTN DN21215 a). In response, the VAP 103 sends a Feature Request[FlashWithInfo] 1924 message to NSP 106 to request completion of thecall transfer and send an IS-136 Flash with Info Ack 1925 message to MS101 to acknowledge the call transfer completion request by the MS 101user. Then NSP 106 determines that this is a call transfer completionaction request, and sends a Feature Request ACK[Transfer (CR=2)] 1926acknowledgment message back to VAP 103 indicating that the CallReference to be transferred equals to 2 (CR=2). VAP 103 then requestsLDS 104 to complete the call transfer by sending a Q.931 Info [CR=2,Transfer] 1928 message to LDS 104, so that the LDS releases from the VAP103 both call references (CR=1 and CR=2), the VAP 103 releases the RF tothe MS, and the transferred call is left in progress between PSTN DN11215 b and PSTN DN2 1215 a (Transferred Call in progress 1937).

To release MS 101, VAP 103 sends an IS-136 Release 1927 message to MS101. In response, MS 101 releases the voice channel air connection withVAP 103 and sends an IS-136 Mobile Ack 1930 acknowledgment message backto VAP 103 indicating that it has been released from the active call. Torelease VAP 103 from the active calls CR=1 and CR=2, LDS 104 sends aQ.931 Disconnect [CR=1] 1929 message and a Q.931 Disconnect [CR=2] 1933message to VAP 103. VAP 103 responds by sending a Q.931 Release [CR=1]1931 message and a Q.931 Release [CR=2] 1934 message to LDS 104. Inreturn, LDS 104 sends a Q.931 Release Complete [CR=1] 1932 message and aQ.931 Release Complete [CR=2] 1935 message to VAP 103 to indicate thatthe LDS 104 has completed the call release process.

Once VAP 103 completes the Q.931 release procedures with LDS 104, itsends a Transfer Complete [Success] 1936 message to NSP 106 to indicateto the NSP 106 that the call is no longer active with mobile station MS101 in the WCS. The Transfer Complete message includes the MSID, the VAPID, the call reference numbers (CR=1, CR=2), and a cause (success/fail)field. At this point the call transfer process has been completedsuccessfully and the active call has been transferred from PSTN DN1 1215b and MS 101 to PSTN DN1 1215 b and PSTN DN2 1215 a.

Referring to FIG. 20, a second preferred embodiment for the WCS calltransfer feature/function shows a call transferred by a mobile stationMS-1 101 a user from mobile station MS-1 101 a to another mobile stationMS-2 101 b within the WCS. In this embodiment, many of the signal flowsin the call transfer process are the same as those in the firstpreferred embodiment for the call transfer feature/function and thushave the same number designations. The primary difference is the callsetup procedure for setting up an incoming call to the second mobilestation MS-2 101 b and its related VAP, VAP2 103 b, as described below.

The signal flow to initiate call transfer of an active call in progressfrom one mobile station MS-1 101 a to another mobile station MS-2 101 bin the same WCS is the same as the signal flow to initiate call transferfrom a mobile station MS 101 to a telephone, PSTN DN2 1215 a outside theWCS. As such, from the point at which a mobile station (MS-1 101 a) userinvolved in an active call in progress (Call in progress, CR=1, 1900)enters the call transfer feature/function activation code by pressingthe digits in the format of *77# with the desired transfer-to DN,TransferDN, followed by the “send” button (results in the MS-1 101 asending an IS-136 Send Burst DTMF[77# TransferDN] 1901 message to VAP1103), up to the point when the active call is placed on hold (Call held,CR=1 1912) and the VAP1 103 a sends the Q.931 Setup [CR=2, TransferDN]1913 message is sent to LDS 104, the signal flows (1901-1913) are thesame. Thus, in the second embodiment of the call transfer WCSfeature/function of the invention, the call transfer is initiated by theMS, authorized by the NSP, and the active call is placed on hold (withappropriate prompt) awaiting further disposition by the WCS, forexample, completed transfer of the held call to a second mobile stationMS-2 101 b as described below.

The Q.931 Setup [CR=2, TransferDN] 1913 message instructing LDS 104 tosetup a second call with the transfer-to DN triggers an AIN query fromLDS 104 to NSP 106 so that a TCAP (AIN Termination_Attempt [TransferDN])2001 message is provided to NSP 106. The NSP 106 verifies the locationof the TransferDN within the WCS. Next, the MS-2 101 b is paged withIS-136 Page Request 2002 message and the VAP1 103 a waits for the Q.931Connect [CR=2] 1920 message from LDS 104 (after the LDS 104 receivesQ.931 Call Proceeding and Alerting messages). While VAP1 103 a waits avoice channel connection with MS-2 is established as follows.

After MS-2 101 b receives the IS-136 Page Request 2002 message, MS-2 101b send an IS-136 Page Response 2003 message to VAP2 103 b and VAP2 103 bsends Page Response 2004 message to NSP 106. This triggers an AINmessage, TCAP (AIN Forward_Call [VAP2-FDN], NEL [O_No_Answer]) 2005,sent by NSP 106 to LDS 104. As a result, the NSP 106 has providedrouting instructions that direct LDS 104 to forward the active call onhold to the Forward Directory Number (FDN) of VAP2 (i.e., VAP2-FDN). NSP106 has also indicated with this message its interest in event(O_No_Answer for VAP2-FDN) by sending next event list NEL [O_No_Answer])information to LDS 104 in the Request component that accompanies theRouting component.

LDS 104 then starts a No Answer Timer (T(NoAnswer)) for VAP2-FDN (notshown) and sends an ISDN Q.931 Setup [CR=2, FDN] 2006 message to theVAP2 103 b. VAP2 103 b then sends a Digital Traffic Channel (DTC)Designation 2007 message to the MS-2 101 b designating the trafficchannel to be used and an ISDN Q.931 Call Proceeding 2009 message to theLDS 104 that triggers the Q.931 Call Proceeding 2010 message sent toVAP1 103 a. MS-2 101 b then tunes to the traffic channel and responds toVAP2 103 b with an IS-136 Mobile on DTC 2008 message. VAP2 103 b detectsthat the MS 101 is on the appropriate traffic channel. VAP2 103 b thenalerts MS-2 101 b with an Alert-with-info 2011 message and MS-2 101 backnowledges with an IS-136 Mobile ACK 2015 message. VAP2 103 b alsosends an ISDN Q.931 Alerting 2012 message to LDS 104 which triggers aQ.931 Alerting 2013 message to VAP1 103 a. Meanwhile, the LDS 104 issending a Ringback Tone 2014 to MS-1 101 a user.

When the MS-2 101 b answers (before T(NoAnswer) timer expires) the MS-2101 b generates an IS-136 Connect 2016 message to the VAP2 103 b and theVAP2 103 b sends an ISDN Q.931 Connect message 2017 to the LDS 104 inresponse to the IS-136 Connect 2016 message from MS-2 101 b. At thispoint the call transfer procedure continues the same as in the previousembodiment so that the MS-1 101 a user can enter the appropriate keysequence to instruct the WCS to complete the call transfer process(steps 1920-1937). As a result, the active call in progress (CR=1)between PSTN 1215 and MS-1 101 a is transferred so that the active callin progress is between PSTN 1215 and MS-2 101 b.

It should be appreciated that transferring a call from a mobile stationin one WCS to a mobile station in another WCS could also be achieved bythe NSP 106 providing the LDS 104 with routing instructions including aFDN indicative of a VAP 103 and MS 101 in the other WCS. Such a casecould be achieved using a procedure similar to the procedure illustratedin FIGS. 19 and 20.

XIII. Caller ID

The Caller ID feature of the present invention allows display on the MS101 of the originating directory number for the calling party's desk toptelephone (Calling Party Number, DN_(O)) and identity (e.g., name) foran incoming and/or active call, even if the call originates from anotherMS 101. Further, the Caller ID information may include locationinformation, e.g., building number, derived from the forward directorynumber (FDN) of the originating VAP 103 (VAP_(O)). In addition, theCaller ID feature of the present invention may provide the location andidentity of the called MS 101 to the calling party and displayed on thecalling party's MS 101 during an active call. In either case, a NetworkServer Platform (NSP) 106 provides a MS 101 user's desk top phonedirectory number, DN_(O), as their telephone number for Caller ID ratherthan the forward directory number (FDN) associated with an originatingVAP 103, VAP_(O) 103, with which the MS 101 is currently associated.

The caller ID or the calling party identification is the numberassociated with the phone from which the call is originating. The WCSCaller ID feature allows the calling party's phone number, identify, andrelated information to be displayed on the WCS mobile handset, MS 101.

Caller ID for a call originating from a PSTN 125 to an MS 101 in a WCSwill occur much the same way that caller ID occurs entirely within aPSTN 125. The WCS Caller ID feature will present to the MS 101 in theWCS environment all the information that the PSTN 125 passes to the VAP103, e.g., calling party telephone number and calling party name.However, if the PSTN 125 does not pass this info to the VAP 103, (e.g.,caller id blocking), the VAP 103 can not, and does not, present anycalling party information to the MS 101.

Caller ID for a call originating from a WCS MS 101 is different thancaller ID for a call originating from a PSTN 125 because the MS 101 iswireless and is associated with the forward directory number of a VAP103, rather than the directory number (DN) of a stationary telephone.Due to the wireless nature of the MS 101 and its association with a VAP103 (or a number of different VAPs) in a WCS, Caller ID for callsoriginating from an MS 101 in a WCS requires unique treatment in orderto provide a calling party telephone number and name which isrecognizable. In the case that the WCS user has both a desk toptelephone and a MS 101, the problem may be solved by the NSP 106providing the users desk top telephone DN for Caller ID purposes,regardless of what VAP 103 the MS 101 is associated with at any point intime. Alternatively, if the MS 101 user does not have a desk toptelephone within the WCS the NSP 106 may be programmed to provide anytelephone number, for example the MS 101 user's home number, thebusiness main number, or the FDN of the VAP 103 to which the MS 101 iscurrently associated. Although the Caller ID feature/function of thepresent invention will be described with respect to a call between oneMS 101 and another MS 101 having the same NSP 106, one skilled in theart will recognize that Caller ID for an MS 101 originating a call maysimilar be provided if the mobile stations 101 have different NSPs 106which can communicate so as to pass the Caller ID information to oneanother.

The preferred embodiments of the WCS Caller ID feature/function providescalling party information to the called party (e.g., phone number, name,address, building number, etc.) for a call between two WCS users, e.g.,an originating mobile station, MS_(O) 101, and a terminating mobilestation, MS_(T) 101. This intelligence is managed by the NSP 106 andthus also enables called party information to be provided to the callingparty, e.g., location of the called party. Three preferred embodimentsare provided below: (1) the intelligence of the NSP 106 is used tocorrelate originating and terminating call legs of a call and sends theappropriate caller ID information; (2) an information element in thecall control message, such as the Q.931 Calling Party Subaddressinformation element of the Setup message, is used to provide caller IDinformation; and (3) a signaling protocol that supports non-callassociated temporary signaling for user to user data transfer, e.g., theQ.931 User Information message, is used to provide caller IDinformation. These embodiments are merely exemplary.

Providing the Caller ID features/functions for WCS to WCS calls can besimplified into two general tasks. First, the NSP 106 must be updatedwith the originating party information of every call that originatesfrom a WCS MS 101. This can be done during the call origination andhence we categorize these tasks as being included in the callorigination leg. To provide the terminating VAP, VAP_(T) 103 with thisinformation (the Caller ID information). These tasks can be categorizedas the one that must be performed during the call termination leg.

A first preferred embodiment will now be described with reference toFIGS. 21A-21D. This embodiment depends on the intelligence of the NSP106 to provide the correct Caller ID information. For a WCS (e.g.,MS_(O) 101) to WCS (e.g., MS_(T) 101) call, the NSP 106 must perform thefollowing two functions. First, the NSP 106 maintains originating partyinformation of every originating call that terminates to a WCS user.Second, for every incoming call, the NSP 106 correlates the terminatingleg of the call with the corresponding originating leg so as to retrievethe originating party information and pass this information to theterminating VAP_(T) 103 to be provided to the terminating MS_(T) 101.These functions require the NSP 106 to track the originating calls andmatch them to the correct terminating portion of the call.

As indicated above, providing caller ID information for this preferredembodiment splits the processing in two legs—the origination request(leg) and the termination request (leg). The information regarding thecaller of each call originated is recorded at the NSP 106 and during thetermination of any call (in this case within the WCS); the caller idrelated information is extracted based on the calling VAP's 103 FDN.

Referring now to FIG. 21A, a flowchart for caller ID informationretrieval procedure is provided and shows the origination leg of the WCSCaller ID feature/function according to a first preferred embodiment.When a call originates from a WCS subscriber's originating MS_(O) 101 toanother WCS subscriber's terminating MS_(T) 101 (for simplicity, bothMSO 101 and MS_(T) 101 are served by the same NSP 106), as a first stepin the origination leg, step 2101, the MS_(O) 101 originates a call toMS_(T) 101. Next, at step 2102 the VAP 103 will send the WCS originationrequest, which will contain the FDN associated with the serving VAP 103to the NSP 106, along with the originating MS_(O) 101 id, i.e. MSID.Then, at step 2103, the NSP 106 uses the MSID to determine whether theWCS user (MS_(O) 101) is registered within the WCS. If not, the NSP 106rejects the MS origination at step 2104. If the MS_(O) 101 is registeredwith the WCS the NSP at step 2105 determines if the MSO 101 has called(requested) a WCS number as the terminating number DN_(T). If not, theNSP 106 follows the normal call processing at step 2107 and sends anorigination ack message. However, if the NSP 106 determines that thecalled termination number DN_(T) is within the WCS, the NSP extracts theDN_(O), i.e. the DN of the desktop associated with the MSID of theoriginating MS_(O) 101 and records the originating user informationalong with the DN_(T), at step 2106, in a Caller ID table. This mappingbetween the MSID and the corresponding DN can be found in the subscriberinformation in the WCS database (WCSD). Thus, the NSP 106 in step 2106stores the DN_(O) and the FDN information against the DN_(T), i.e. theDN of the phone where the call has to terminate, in a record andsubsequently continues the normal call processing by, for example,sending an origination acknowledgement message in step 2107.

Referring now to FIG. 21B, when the call comes to the termination legthe LDS 104 at step 2108 sends, for example, an AIN TAT message to theNSP 106 which includes, for example, the DN_(T) and the FDN of theoriginating VAP, VAP_(O) 103, information in it. Next, in step 2109, theNSP 106 checks to determine that the Caller ID table in the WCSD has anentry for the DN_(T) which matches the originating FDN. If there is amatch of the DN_(T) and the FDN, the NSP 106 retrieves the caller IDinformation, for example, the desktop telephone directory number DN_(O)for the originating mobile station, MS_(O) 101, and sends it to thetermination VAP, VAP_(T) 103, in, for example, a page request message,as shown at step 2110. Then, the caller ID information, for example,DN_(O), may be sent by the VAP_(T) 103 to the MS_(T) 101 in, forexample, an IS-136 Alert with Info message. As a result, the MS_(T) 101will display the caller ID information, for example the DN_(O), on theMS_(T) 101.

On the other hand, if at step 2109, the NSP 106 does not find a callerID match for the DN_(T) with the originating FDN or there is nospecified DN_(O) within the database for MS_(O) 101, the NSP 106 sends,for example, a page request message to the terminating VAP_(T) 103without a DN_(O). Then, at step 2113, the VAP_(T) 103 sends the callingparty number contained in, for example, a Q.931 Setup message, which maybe the FDN of the originating VAP. It should be noted that the DN_(O)related information can be stored at the NSP 106, and can be used forthe other features like call return, call screen etc for this call.

Clearing of the calling party number related information records fromthe NSP 106 may be handled as follows. The caller id related records arecreated during the call origination and may be cleared off during calltermination. Certain information may be required to be updated at theNSP 106 before the caller id related record is cleared. For instance,the “last calling party number” is needed for call return feature; hencea field holding this value shall be updated. The caller id record for acall may be cleared from the NSP 106, if any of the following occur: (1)when NSP 106 has paged the MS 101 with the DN_(O) information, (2) whena call fails during the origination attempt, (3) when the call isdelivered to the desktop phone, and (4) when the call is treated as thewaiting call in case of the call-waiting feature (that is, when NSP 106notifies VAP 103 of call waiting. Furthermore, all the records mayinclude a time stamp of the time when they are created, and the WCS mayinclude periodic checking for the time stamps which are older than acertain amount of time, which if found, such records would beautomatically and periodically cleared.

Referring to FIGS. 21C and 21D, exemplary signal flow diagrams areprovided for a call origination and termination within the WCS for thefirst preferred embodiment of the Caller ID feature/function. Asindicated by the flowcharts in FIGS. 21A and 21B, implementation of theCaller ID feature/function in this embodiment requires some additionalthings be done beyond the normal signal messages exchanges between VAP103, NSP 106 and LDS 104.

An exemplary signal flow for the call origination leg of the firstpreferred embodiment for the Caller ID feature/function is illustratedin FIG. 21C. During call origination the originating WCS MS, MS_(O) 101,requests for the call origination by sending an IS-136 Origination 2114message including an MSID to the VAP_(O) 103 followed by optionally anIS-136 Serial Number message 2115 which includes the electronic serialnumber (ESN) of the MS_(O) 101. Then VAP_(O) 103 sends an OriginationRequest 2116 message to the NSP 106. The Origination Request 2116message contains the Called party id i.e., DN_(T), the FDN of theoriginating VAP_(O) 103, and the identification of the originatingMS_(O) 101 MSID and/or the ESN. The NSP 106 validates the originatingMS_(O) 101 and checks whether the termination directory number, DN_(T)is a WCS subscriber. If it is, then NSP 106 searches the WCSD for aDN_(O) of the MS_(O) 101 associated with the MSID and, if one exists,extracts and records the DN_(O) of the MSID as being correlated to thedestination (termination) DN, DN_(T), as indicated in step 2117. Inother words, the NSP 106 retrieves the DN associated with theoriginating MSID, e.g., the DN_(O), and records the FDN and the DN_(O)against the called party DN, e.g., DN_(T). Next, the NSP 106 sends theOrigination Ack 2118 message. Subsequently, signaling 2119-2127,illustrate normal Call processing to completion of a voice path betweenthe MS_(O) and the MS_(T) (2128). Thus, the signal flow for signaling2119-2127 is similar to the usual origination call flow as described inthe call processing section above (see, for example, FIG. 4 and itsrelated description).

Referring now to FIG. 21D, an exemplary signal flow for the calltermination leg of the first preferred embodiment for the Caller IDfeature/function is illustrated. First, since in this case the incomingcall is from another MS, MS_(O) 101, within the WCS, a Q.931 setupmessage (triggered by, for example, Q.931 setup 2119 message) isreceived by the LDS 104 (not shown in figures). Alternatively, if theincoming call is from PSTN 125 an ISUP LAM message will be received bythe LDS 104. In either case, the LDS 104 recognizes the incoming call asbeing directed to an MS 101 and thus sends an MN TAT message, TCAP (AINTermination_Attempt [DN_(T), FDN]) 2129, to the NSP 106 so that the NSP106 can provide information to the LDS 104 regarding the presentlocation of the MS 101 associated with the termination directory number,DN_(T), so as to properly route the call. As illustrated, the AIN TATmessage will contain the DN_(T), i.e., the called party ID, and thecalling party number, which is the FDN of the originating VAP_(O) 104 inthe case where the call originates within the WCS.

Next, the NSP 106 attempts to match the originating terminal id, in thiscase the FDN of the originating VAP_(O) 103 for this AIN TAT message,against the FDN, DN_(T) pairs stored within its records (during the callorigination leg). If there is a record with a matching FDN for thedesignated DN_(T), the NSP 106 will extract the previously stored callerID information, for example DN_(O), from the WCSD and send it to thetermination VAP, VAP_(T) 103, in a Page Request [MSID, DNO] 2131message. If no match is found, then DN_(O) shall not be populated andthe VAP_(T) 103 shall receive the calling party number provided in theQ.931 setup message (e.g., a PSTN 125 DN or a VAP 103 FDN). In essence,if there are no records with matching FDN, then there is no specialinformation sent to the VAP_(T) 103 in the Page Request 2131 message andVAP_(T) 103 will present the calling party number information it getsfrom the Q.931 messages to the MS_(T) 101. In any case, the usual callprocessing procedures follows at steps 2131-2141.

Then at step 2141, the VAP_(T) 103 sends the caller ID information tothe MS_(T) 101 to, for example, display the caller ID information to theMS_(T) 101 user. In the case there is a match, the VAP_(T) 103 sends anIS-136 Alert with Info [DNo] 2141 message to the MS_(T) with, forexample, the DN_(O) information and/or other caller ID information (fromPage Request 2131 message or the Q.931 setup message) to provide theMS_(T) 101 user with the caller ID information, which in the case is thecaller ID information for the originating MS_(O) 101 user (e.g., theDN_(O) of the MS_(O) 101 user's desk top telephone). If there is nomatch, the VAP_(T) 103 sends an IS-136 Alert-with-Info 2141 message tothe MS_(T) 101 with the calling party number value from the Q.931 Setup2137 message. Subsequently, at steps 2142-2150, the call processing forthe Caller ID termination leg for this embodiment is similar or the sameas those mentioned for a general call termination in the call processingsection above (see, for example, FIGS. 5-7 and their relateddescription).

A second preferred embodiment for the Caller ID feature/function willnow be described with reference to FIGS. 21E-21H. This embodiment doesnot depend on the intelligence of the NSP 106 to provide the correctCaller ID information. Once again, this embodiment also splits theprocessing in two legs—the origination request (leg) and the terminationrequest (leg). In this case the WCS relies on existing signalingprotocol to forward the caller ID information without storing andsubsequently matching the data in the WCSD for the originating VAP_(O)103 FDN and the termination MS_(T) 101.

In this preferred embodiment, the caller ID information regarding thecaller of each call originated (e.g., the DN_(O) associated with theoriginating MS_(O) 101) is sent by the NSP 106 to the originatingVAP_(O) 103 in, for example, the Origination Ack. The NSP 106 does notset up a record in the WCSD but merely extracts the caller IDinformation, for example the DN_(O), from the WCSD and sends it to theoriginating VAP_(O) 103. The VAP_(O) 103 then sends the calling partycaller ID information (e.g., DN_(O)) in an available field of anexisting message sent to the LDS 104, for example, the subaddress IE ofits Q.931 Setup message sent to the LDS 104. Subsequently, during thetermination leg, the LDS 104 preserves and forwards this caller IDinformation to the terminating VAP_(T) 103 in an existing call setupmessage, for example, in the subaddress IE of a Q.931 setup message thatthe LDS 104 sends to the terminating VAP_(T) 103. This information cannow be presented by the terminating VAP_(T) 103 to the terminatingMS_(T) 101 through an existing call setup message, for example, an Alertwith Info message. This general method of the second preferredembodiment is described in more detail below.

Thus, this approach is dependent on the ability of using an informationelement field of a call control message passed from the originatingVAP_(O) 103 to the destination VAP_(T) 103. An example of this is theQ.931 Calling Party Subaddress field of the Q.931 Setup message. Thisfield can be use to carry caller ID information regarding the callingparty, such as the DN of the desktop phone associated with theoriginating MS, caller's name, caller's address, caller's location, etc.

Referring to the flowchart in FIG. 21E, the process for the originationleg of the second preferred embodiment of the Caller ID feature/functionis illustrated and will now be described. Once again, the embodimentillustrates a scenario for a call originating from a WCS subscriber'sMS, the originating MS_(O) 101, to another WCS subscriber, terminationMS_(T) 101. First, at step 2151, the user of an MS 101 originates acall. Then, at step 2152, the VAP 103 sends a message to the NSP 106,for example, a WCS origination request message, which may contain theoriginating phone's ID, i.e. MSID, and the called party number, e.g.,DNT. Next, at step 2153, the NSP 106 determines whether the MS 101 useris registered with the WCS. If the MS 101 is registered and valid, instep 2155 the NSP 106 retrieves the caller ID information, e.g., DN_(O)(the DN of the desktop associated with the MSID) by accessing themapping between the MSID and the corresponding DN which may be storedin, for example, the subscriber information in WCSD. The NSP 106 alsoforwards the caller ID information (e.g., DN_(O)) to the VAP 103 in atypical call setup message, for example, an origination ack message.Then in step 2156, the originating VAP_(O) 103 sends the caller IDinformation (e.g., DN_(O)) to the LDS 104 in an available field ofanother typical call setup message, for example, the subaddress IE fieldof a Q.931 Setup message. However, if the MS_(O) 101 is not a registereduser, the NSP 106 will reject the origination message at step 2154.

Referring now to the flowchart in FIG. 21F, the process for thetermination leg of the second preferred embodiment of the Caller IDfeature/function is illustrated and will now be described. First, instep 2157 the LDS 104 sends a typical call setup message, for example anAIN TAT message, to the NSP 106 so as to terminate the call at theDN_(T) originated by the DN_(O). At step 2158 the NSP 106 responds bysending a typical call setup message to the VAP_(T) 103 to which thetermination MS_(T) 101 is presently associated, for example a PageRequest message. The VAP_(T) 103 responds by sending a typical callsetup message indicating that the desired MS_(T) 101 is available via aPage Response message The NSP 106 instructs the LDS 104 to forward theincoming call to VAP_(T) 103 using, for example, an AIN Forward_Callmessage. At step 2159, the LDS 104 sends a typical call setup message tothe terminating VAP_(T) 103, for example a Q.931 Setup message. Sincethe originating VAP_(O) 103 put the caller ID related info (e.g.,DN_(O)) in the subaddress IE of the Q.931 SETUP message, this info willbe contained in, for example, the subaddress IE of the Q.931 SETUP sentfrom the LDS 104 to the terminating VAP_(T) 103. As indicated at step2160, if the subaddress IE field is populated with caller IDinformation, for example DN_(O) for the calling MS 101, the VAP_(T) 103will receive the information and provide it to the MS_(T) 101 via atypical call setup message, for example an IS-136 “Alert with Info”message. Otherwise, the VAP_(T) 103 shall use the Calling party numberinformation, e.g., the VAP_(O) 103 FDN or the PSTN 125 DN from the Q.931SETUP message.

Referring now to FIG. 21G a detailed signal flow diagram for anorigination leg of the second preferred embodiment of the Caller IDfeature/function will now be described. First, an originating WCS MS,MS_(O) 101, requests for call origination by sending an IS-136Origination 2161 message and an optional IS-136 Serial Number 2162message containing the ESN to the originating VAP_(O) 103. Then, theoriginating VAP_(O) 103 sends an Origination Request [MSID, DNT] 2163message to the NSP 106. The Origination Request message contains theCalled party ID, DN_(T), FDN of VAP_(O) and the identification of theoriginating MS_(O) 101, MSID and/or the ESN. Next, the NSP 106 validatesthe MS_(O), and retrieves the caller ID information, for example aDN_(O), associated with the MSID. The NSP 106 sends the caller IDinformation, e.g., DN_(O), to VAP_(O) 103 in an available field of theOrigination Ack [DN_(O)] 2165 message.

Then the VAP_(O) 103 sends the caller ID information, e.g., DN_(O), thatit received from the NSP 106 in the Calling Party Subaddress IE of theQ.931 Setup [Subaddress IE =DN_(O) info] 2166 message that it sends tothe LDS 104. The LDS 104 will setup the call to DN_(T) (this willtrigger an AIN message in the terminating leg signal flow (see FIG.21H)). Subsequently, signaling 2167-2174, illustrate normal callprocessing to completion of a voice path between the MS_(O) and theMS_(T) (2175). Thus, the signal flow for signaling 2167-2174 is similarto the usual origination call flow as described in the call processingsection above (see, for example, FIG. 4 and its related description).

Referring now to FIG. 21H, the signal flow for the terminating portionof an exemplary second preferred embodiment for a WCS MS to WCS MS callwill be described. As indicated above, the originating MS_(O) 101 usercalls another WCS MS 101 subscriber's DN, the terminating DN_(T), and asa result the LDS 104 receives a Q.931 Setup [subaddress IE DN_(O) info]2166 message. The LDS 104 finds that the DN_(T) is provisioned for AINTermination Attempt Trigger (TAT). As a result, the LDS 104 suspends thedelivery of the call and sends an AIN query message, TCAP (AINTermination Attempt [DN_(T), FDN]) 2176, to the NSP 106 for appropriaterouting instruction based on the last known location of MS_(T) 101. NSP106 finds that the subscriber's MS 101 (MS_(T)) associated with DN_(T)is active and idle in its serving area, associated with VAP_(T) 103. NSP106 pages the MS_(T) 101 through VAP_(T) 103 with IS-136 establishedpaging procedures, e.g., Page Request [MSID] 2178 and IS-136 Page 2179,and starts TT6 timer. As a part of the Page Request 2178 message, theNSP 106 shall send the Mobile's MSID. MS_(T) 101 sends an IS-136 PageResponse 2180 message followed optionally by IS-136 Serial Number 2181message. When MS_(T) 101 responds to the page, VAP_(T) 103 selects a FDNfor the call, and forwards it in a Page Response [FDN] 2182 message tothe NSP 106, and starts event timer TT10. Upon reception of PageResponse [FDN] 2182, the NSP 106 will cancel TT6 timer and knows thatthe current VAP_(T) 103 has the resources to serve the incoming call.

Next, the NSP 106 directs the LDS 104 to forward the call to the FDN (ina TCAP Conversation package) by sending the LDS 104 a TCAP (AINForward_Call [FDN], NEL [O_No_Answer]) 2183 message. The NSP 106indicates its interest in event (O_No_Answer for FDN) by sending nextevent list (NEL) information to the LDS 104 in a Request component,which accompanies the routing component, in the conversation package.The LDS 104 will start No Answer Timer (T(NoAnswer)) for FDN and send aQ.931 Setup [FDN, Subaddress IE =DN_(O)] 2184 message to VAP_(T) 103.When VAP_(T) 103 receives the Q.931 Setup [FDN, Subaddress IE =DN_(O)]2184 message, it will cancel the TT5 timer, initiate an IS-136 DTCDesignation 2185 message to MS_(T) 101, start the TT2 timer, and send aQ.931 Call Proceeding 2186 message to the LDS 104. VAP_(T) 103 willretrieve the calling party information first from Q.931 Calling PartySubaddress IE indicating that this call is from a WCS MS (refer to theQ.931 Setup [FDN, Subaddress IE =DN_(O)] 2166 message in the originatingcall leg signal flow shown in FIG. 21G). If the subaddress is notpopulated then VAP_(T) 103 will attempt to retrieve the calling partyinformation from the Q.931 Calling Party IE indicating that this call isfrom the PSTN 125 or a VAP 103 FDN. If neither fields are populated, thecalling party information can not be retrieved and therefore can not bepresented to the called party.

Next, the VAP_(T) 103 sends a DTC Designation 2185 message to the MS_(T)101 and the MS_(T) 101 tunes to the traffic channel, MS on DTC 2187.When VAP_(T) 103 detects that MS_(T) is on the traffic channel via DVCCstatus change, it will initiate the Alerting procedures to both calllegs (i.e., the LDS and MS directions). Then VAP_(T) 103 sends an IS-136Alert-with-info message to MS_(T) 101 along with the retrieved callingparty caller ID information (if any) for example IS-136 Alert-with-info[DN_(O)] 2188 message, and start the Alert timer (TT3). When MS_(T) 101receives the Alert-with-info message, it may notify the user with analert, e.g., via ringing. MS_(T) 101 then sends an IS-136 Mobile ACK2189 message to the VAP_(T) 103. When VAP_(T) 103 receives the MobileACK 2189 from MS_(T) 101, it will cancel TT3 timer and start TT4 timer,and enters the wait-for-answer call processing state. Subsequently, atsteps 2190-2197, the call processing for the Caller ID termination legfor this embodiment is similar or the same as those mentioned for ageneral call termination in the call processing section above (see, forexample, FIGS. 5-7 and their related description).

A third preferred embodiment for the WCS Caller ID feature/function issimilar to the second preferred embodiment and uses existing signalingmessages to coordinate the caller ID information. This preferredembodiment is dependent on a signaling protocol that permits exchange ofuser to user data. For example, in addition to the normal call setupprocedure described above, the originating VAP_(O) 103 uses the Q.931non-call associated signaling procedure to send the calling partyinformation to the destination (termination) VAP_(T) 103 before thedestination VAP_(T) 103 sends the IS-136 Alert-with-Info message. Thus,in this embodiment it is not necessary to use the Calling AddressSubaddress IE field. The WCS Caller ID feature/function invention mayprovide caller ID information whether the call is from one MS 101 toanother MS 101 associated with the same NSP 106 or different NSPs. Inthe case of different NSPs, the process must include a means oftransferring or sharing of the caller ID information, e.g., DN_(O)between the various NSPs. Further, the WCS MS 101 caller ID informationmay also be provided to a call to a PSTN 125 user as long as a means isprovided for entering the caller ID information related to the MS 101DN_(O) into the signaling between the PSTN 125 and the WCS.

Further, the WCS Caller ID feature/function of the present invention mayprovide for the calling party to be initially coupled with a voice pathto, for example, a voice processing unit (VPU) including voicerecognition capabilities, which is located in, for example, the VAP 103.As such, the calling party can provide their name or other informationwhich will be provided to the called party, by for example, display onthe MS of the called party. The Caller ID feature/function may alsoallow display on the MS 101 or audio presentation of additionalinformation about the calling or called party, for example theiraddress, building number, company affiliation, etc. for an incoming oractive call. Thus, the WCS of the present invention provides a MS 101user with the ability to know the identity of the calling persons beforeanswering a call and the desk top telephone number, identity, location,etc. of a calling party or a party they are speaking with on an activecall, even in the case when the calling party is calling from a WCS MS.

XIV. Screening Calls

The advent of any time and any place communications provided by thepresent invention brings with it certain conveniences and certaininconveniences or annoyances. Ideally, the invention should minimize theinconveniences or annoyances. One convenience is that anyone, forexample a solicitor, can call a mobile station at anytime, or example inthe middle of an important meeting. Therefore, there is a need toprovide the mobile station user in a WCS the ability to block outincoming calls from particular phone numbers, for example, directorynumbers.

The call screening feature/function of the instant invention providesjust such a means for screening calls in a Wireless Centrex Services(WCS) System. More specifically, the invention allows a mobile stationuser to specify a list of phone numbers (call screen list) from whichincoming calls can be blocked when received. When any one of the phonenumbers in the list is calling the MS 101, based on the MS 101 user'sprevious instructions the WCS system will block the call and either sendthe call to a message answering service (e.g., a VMS 107), send the callto intelligent peripheral (IP) device (e.g., a VPU 1235 or a DSP) whichwill provide a pre-recorded announcement message, or just simply dropthe call without providing the calling party any announcement orrecourse.

The call screen list of phone numbers can be added to or modified usinga number of different methods. In one exemplary embodiment, a MS userenters the phone number manually from the MS 101 by keying in each digitof the phone number to be blocked. The MS 101 user dials a featureactivation code, for example, *60#, followed by the phone number that isto receive the call screening treatment, followed by the send button(e.g., *60#5551212). In response, the WCS system adds the phone number(e.g., 5551212) to the Call Screen list and activates the call screenfeature for the phone number entered. This confirms the featureactivation.

In another exemplary embodiment of the call screen feature/function ofthe invention, the call screen list can be added to or modified bypressing a particular key on the MS 101 or by entering the feature codewithout a phone number, after an active call is disconnected (e.g.,after an unwanted incoming call is received). In this case, as anexample, the user can key in the feature code, e.g., *60#, on the MS 101and press the send button after a call is hung up. The WCS will retrievethe last active call's related phone number from its database and add itto the call screen list for the MS.

In either of the previous embodiments, a MS user can remove a particularphone number from the Call Screen list or turn off the call screenfeature by, for example, pressing a button on the MS 101 or keying intothe MS 101 a particular feature code, with or without a phone number tobe removed from the Call Screen list. For example, a MS user may keyinto the MS 101 a Call Screen feature deactivation code, for example*600#, and the phone number and press the send button. As a result anincoming call to that particular phone number will no longer receivecall screen treatment. Alternatively, if the MS 101 user enters a CallScreen feature deactivation code, for example *600#, without enteringalong with it a phone number, all call screen treatment will bedeactivated for all phone numbers on the Call Screen list.

In yet another embodiment for the call screen feature/function of theinvention, the Call Screen list can be added/modified via the internet(World Wide Web) or by calling the WCS CSC representative. A moredetailed discussion of the call screen feature/function of the presentinvention follows.

Referring to FIG. 22, a signal flow for provisioning (activating) thecall screen feature/function will now be discussed using the embodimentwherein the MS 101 user enters a feature code and phone number via theMS 101 to activate call screening to block an incoming call. In general,the signal flow for provisioning the call screen feature may follow themethods discussed previously for feature activation. First, the MS 101user enters the feature activation code and number on the keypad of anMS 101, such as, 60# CallScreen DN, where CallScreenDN is the desireddirectory number (i.e., phone number) to be screened out (i.e., the MS101 user will not know about the call at the time the incoming calloccurs). As a result an IS-136 Origination [*60# CallScreenDN] 2201message is sent from the MS 101 to the VAP 103 over the Reverse DigitalControl Channel (RDCCH) wherein the called party number field is set toCallScreenDN. The VAP 103 receives the IS-136 Origination [*60#CallScreenDN] 2201 message and sends an Origination Request [*60#CallScreenDN] 2202 message to the NSP 106 and starts the originationcomplete timer T01. The Origination Request [*60# CallScreenDN] 2202 isunique in that the Dialed Digit IE (field) which normally contains a DNthe MS 101 user wishes to connect to, now contains the feature code *60#and the incoming DN to be screened, CallScreenDN.

The NSP 106 receives the Origination Request [*60# CallScreenDN] 2202message, performs an analysis of the dialed digits and determines thatit is actually a feature request, i.e., a Call Screen request, ratherthan a telephone call. Next the NSP 106 proceeds to check against theservice profile in the WCSD (stored in, for example, the memory 1240)via the MIN of the MS 101 to determine whether the MS 101 is authorizedfor the Call Screen feature. If the validation is successful the NSP 106updates the feature activation table for the particular MIN and sends acall origination not acknowledged message, Origination NACK [Cause,Display] 2203 to the VAP 103 which includes proper text informationpertaining to the feature, e.g., Call Screen active and the number ofthe DN that is programmed to be screened. Alternatively, the informationcontained in this message could be provided via a short message formatsuch as an SMDPP message (similar to an IS-41 message). Next, the VAP103 sends an IS-136 Reorder/Intercept [Display] 2204 message to the MS101. This message contains status information regarding the MS 101user's request to block a call with the call screen feature/function.For example, the Display information may contain the statement “CallScreen active for CallScreenDN. Similar to the Origination NACK message,the IS-136 Reorder/Intercept message is generated as a result of atelephone call setup is rejected because the numbers dialed by the MS101 user to activate the call screen were not a recognizable DN forwhich a telephone call could be established. Thus, the Display field ofthis message is modified to carry the information to indicate to the MS101 user the status of their call screen request.

On the other hand, if the NSP 106 determines that the MS 101 is notauthorized to use the Call Screen feature, it will send a messageOrigination NACK [Cause, Display] 2203. message with proper rejectinformation in the cause (e.g., text) field (Call Screen Not Available)to the MS 101. After receiving the Origination Request message 2203 fromthe VAP 103 to the NSP 106, an Origination NACK message will be sent tothe VAP 103 and the VAP 103 will then cancel the timer TO1, release theMS 101, and clear the origination request record.

As previously indicated, if the MS 101 user does not enter aCallScreenDN at the time of initiating the call screen feature, then theWCS will determine the DN for the last active call to which the MS 101was a party, and activate a call screen for that particular DN. In thecase when the DN is not specified and the last active call was anincoming call, the NSP 106 will use the last incoming Caller ID toactivate call screening. If the last caller ID is available, the NSP 106updates the feature activation table for the particular MIN and sends anOrigination NACK [Cause, CallScreenDN] 2203 message with proper text andthe CallScreenDN information to inform the MS that calls from theidentified CallScreenDn will be screened. Otherwise, if a Caller ID forthe previous active call can not be determined the NSP 106 will notifythe VAP and MS 101 that the call screen feature has not been activated.

The call screen feature/function also includes a feature that allows theMS 101 user to determine the disposition of an incoming call which isblocked because the incoming call DN is included in the Call Screenphone number list. The MS 101 user can pre-program the WCS by entering afeature programming code associated with a particular manner for the WCSto handle an incoming call after it is blocked by a call screendesignation (i.e., call screen treatment). For example, the MS 101 usercan provision the DNs that he would like to screen and the manner inwhich the call coming from a CallScreenDN may be treated by manuallyentering particular feature/function codes on the MS 101. Theprovisioning can also be done through the WCS web site or by calling aCustomer Service Center (CSC) representative. Below are illustrations ofmethods by which the MS 101 user can pre-program the CallScreenDN listby himself/herself using the MS 101. The exemplary provisioningmechanism are as follows.

To provision the Call Screening list, the MS 101 user may dial forexample *60#n#DN, where n is a number between 1 and 3 and signifies thecall screen treatment, and DN is the CallScreenDN telephone number, thenpress the “send” button (e.g. *60#1#5551212). The correspondence betweenthree possible call screen treatment codes and the treatment to beexecuted is provided in the table below.

TABLE 3 Code Treatment description 1 Disconnect the call 2 Forward thecall to the specified resource (e.g., VMS) or DN 3 Play voiceannouncement that “called party unavailable”

Alternatively a desired CallScreenDN can be dynamically added to thelist of CallScreenDNs after an unwanted call is received. The MS 101user can press *60#n and the “send” button during or immediately afteran active call is released. In response, the WCS will retrieve thecalling party number and add it to the call screen list for the MS 101.If no number is specified to indicate the type of call screen treatmentdesired (e.g., 1, 2, or 3) while provisioning (e.g., *60##DN) a defaultwill be set, for example, the type 1 call screen treatment will beprovided for calls coming from the entered CallScreenDN (DN input withthe feature code *60). Further, to remove a particular phone number fromthe list, the MS 101 user may dial for example *600#DN, where DN is theCallScreenDN telephone number, and press the “send” button. To removeall the entries from the table, the user may press, for example, *600#*.

Thus, the user of MS 101 can enter a feature programming code, forexample, *601# with a phone number being screened, CallScreenDN, andpress, for example, the send button to program the incoming call to bedropped without any announcement to the calling party. This featureprogramming code would be stored in the WCSD and be associated with theCallScreenDN to which it relates. The signal flow for this added featureprogramming would be similar to the signal flow for Call Screen featureactivation illustrated in FIG. 22. If the MS 101 completes such CallScreen feature programming by entering *601#, when an incoming calloriginates from the CallScreenDN phone number, the WCS will drop theblocked call without playing any announcement.

Different feature programming codes, for example, *602#, *603#, etc.,could be used to program the WCS to dispose of a call screen blockedcall by sending it to a VMS 107 or playing an announcement to thecalling party indicating that the call is being blocked, etc. Further,the WCS can be programmed so that any one of these call screentreatments (as well as any other not mentioned herein) is used as thedefault Call Screen blocked call disposition. A detailed discussion ofthe signal flow for some of the possible disposition of incoming callsblocked by the Call Screen feature follows.

In accordance with one preferred embodiment of the invention, FIG. 23illustrates an exemplary call screen treatment wherein an incoming calloriginating from a CallScreenDN is terminated without any announcementto the calling party. Although, this embodiment shows an incoming calloriginating from a DN in the PSTN 125, a similar signal flow would occurfor a call originating from a DN in a WCS.

When, for example, a PSTN 125 user dials a WCS subscriber's DN from atelephone outside the WCS, the LDS receives an ISUP LAM [DN] 2301message from the PSTN 125 to alert the LDS 104 of an incoming calloriginating from a particular DN. The LDS 104 determines that the calledDN is provisioned for an advanced intelligent network terminationattempt (AIN TAT), suspends the delivery of the call, and sends an AINquery, TCAP (AIN Termination_Attempt [DN]) 2302 message, to the NSP 106for an appropriate routing instruction for contacting the called DN.When the NSP 106 receives the AIN TAT it checks the MS 101 user'sservice profile feature settings in the WCSD to determine whether theoriginating telephone number (calling party DN) is a screened telephonenumber and if so what, if any, Call Screen treatment has been specifiedby the MS 101 user. In this case, the MS 101 has activated the CallScreen feature/function for the originating DN and programmed the callscreen treatment so that the incoming call should be dropped withoutplaying any announcement to the calling party. Therefore, the NSP 106then determines that the attempted DN is directed to a MS 101, and thatthe MS 101 has provisioned the calling party's telephone number as aCallScreenDN with a call screen treatment of dropping the call withoutan announcement.

In response, the NSP 106 sends a TCAP (AIN Disconnect) 2303 message tothe LDS 104. In response the LDS 104 sends the PSTN 125 an ISUP REL 2304message to release the PSTN 125 without any announcement. Then the LDS104 sends the TCAP (AIN Close) 2305 message to close the TCAPtransaction. Finally, the LDS 104 sends the PSTN 125 a ISUP RLC 2306message to indicate a release has been completed.

In accordance with a further embodiment of the invention, FIG. 24illustrates an exemplary call screen call treatment scenario in which anincoming blocked call is sent to a resource, such as an answeringservice, for example VMS 107. In this case, the signal flow is similarto the case where the call screen treatment is set to drop the incomingcall without providing the calling party an announcement. However, inthis case the LDS 104 is instructed to forward the call from theCallScreenDN (calling party number that is provisioned to be screened)to a resource (e.g., VMS 107) for a proper announcement directed to thecalling party.

Once again when, for example, the PSTN 125 user dials the WCSsubscriber's DN, the LDS 104 receives an ISUP IAM [DN] 2301 message fromthe PSTN 125. The LDS 104 finds that the DN is provisioned for AIN TAT,suspends the delivery of the call, and sends an AIN query message, TCAP(AIN Termination_Attempt [DN]) 2302 to the NSP 106 for an appropriaterouting instruction. Then, the NSP 106 checks the WCSD database todetermine whether the calling party telephone number (DN) has beendesignated by the MS 101 user as a screened number and whether the MS101 user has set a call screen treatment. In this case, the NSP 106determines that for the called DN (MS 101) the incoming calling party'stelephone number is a CallScreenDN and the call treatment requires thecall be sent to a resource. So the NSP 106 instructs the LDS 104 thatthe incoming call is to be sent to a resource, such as the VMS 107 whichwill allow the calling party to leave a voice message. Thus, the NSP 106sends a TCAP (AIN SendToResource) 2401 message to the LDS 104. The LDS104 sends a TCAP (AIN Close) 2402 message to the NSP 106 to close theTCAP transaction. Finally, the LDS 104 and VMS 107 (IntelligentPeripheral) assume the call processing (Call processing by LDS and VMS2403) enabling the calling party to leave a message for the MS 101 user.

In accordance with another preferred embodiment of the invention, FIG.25 illustrates a call screen treatment scenario in which a screened callis forwarded to a VAP 103 for playing an announcement to the incomingcall indicating, for example, that the call has been screened and willbe dropped or that the MS 101 user is not interested in the service orproduct being offered by the calling party. The NSP 106 designates whichVAP 103 within the WCS will provide the announcement to the callingparty based on, for example, VAP 103 availability. Therefore, the VAP103 designated to play the announcement is not necessarily the VAP 103with which the MS 101 is presently resident.

When, for example, the PSTN 125 user dials the WCS subscriber's DN, theLDS 104 receives an ISUP LAM [DN] 2501 message from the PSTN 125. TheLDS 104 recognizes that the called DN is set up for an AIN TAT triggerand sends the NSP 106 an AIN TAT query message, TCAP(AINTermination_Attempt [DN]) 2502, to get routing information for theincoming call. The NSP 106 checks the WCSD database to determine whetherthe calling party's telephone number is a CallScreenDN for the MS 101being called and whether the MS 101 user has set a particular callscreen treatment. Assuming that the NSP 106 determines that the callingparty's DN is designated as a CallScreenDN for the MS 101 being calledand the MS 101 user has set a call screen treatment for playing anannouncement to the calling party, the NSP 106 sends a Play AnnouncementRequest [Call Screen, FDN] 2503 message to one of the available VAPs,specifies the type of announcement to be played (i.e., Call Screen: Donot call again!) and starts the TPA1 timer. The message will contain theFDN and the announcement option, Call Screen in this case, along withthe MIN, VAP ID, and call reference number (e.g., CR=1). However, if theNSP 106 does not find any VAP 103 to connect to the calling partyincoming call or the TPA1 timer expires before receiving the PlayAnnouncement Result 2519 message from the VAP 103, it will send a TCAP(AIN Disconnect) message to the LDS 104 and the incoming call will bedisconnected without any announcement.

Next, the NSP 106 sends a TCAP (AIN Forward_Call [FDN]) 2504 message tothe LDS 103 directing the LDS 104 to establish a connection between theincoming call from the calling party and the chosen VAP 103 byforwarding the incoming call to the chosen VAP 103. The LDS 104 thenperforms a call setup between the selected VAP 103 and the incomingcall. First, the LDS 104 sends the VAP 103 a Q.931 Setup [FDN] 2505message. In response the VAP 103 sends a Q.931 Call Proceeding 2506message, a Q.931 Alerting 2507 message, and a Q.931 Connect 2509 messageto the LDS 104. In the meantime, the LDS 104 sends an ISUP ACM 2508message and an ISUP ANM 2510 message to the PSTN 125. When the incomingcall has been properly connected with the selected VAP 103, the LDSsends a Q.931 Connect ACK 2511 acknowledgement message to the VAP 103and a TCAP (AIN Close) 2512 message to the NSP 106.

Once the incoming call is connected with the VAP 103, the VAP 103 playsthe announcement (for example, a default announcement, a user definedannouncement using voice synthesis, or a user defined announcement thatis a recorded message created by the MS 101 user) at step 2513. The VAP103 uses, for example, a DSP to provide the announcement or may utilizethe VPU 1235 in the NSP 106 to generate the announcement. After theannouncement has been played, the VAP 103 initiates a disconnect processwith the LDS 104 and the LDS 104 initiates a release process with thePSTN 125, releasing the VAP 103 and PSTN 125 from the active voicetraffic channel. This process is initiated by the VAP 103 sending theLDS 104 a Q.931 Disconnect 2514 message instructing the LDS 104 todisconnect the active call between the VAP 103 and the PSTN 125. The LDS104 releases the active call connection with the VAP 103 by sending aQ.931 Release 2515 message and releases the active call connection withthe PSTN 125 by sending a ISUP REL 2516 message. The VAP 103 notifiesthe LDS 104 that the call has been disconnected by sending a Q.931Release Complete 2517 message to the LDS 104. The PSTN 125 notifies theLDS 104 that the call has been disconnected by sending an ISUP RLCComplete 2518 message to the LDS 104. Finally, the VAP 103 sends a PlayAnnouncement Result [Success] 2519 message to the NSP 106, indicatingthat the announcement was played successfully for the incoming call, andcancels timer TPA1. The Play Announcement Result message includes a VAPID, FDN, Call Reference Number, Result, and Cause fields. As previouslyindicated, if the TPA1 timer expires before receiving Play AnnouncementResult 2519 message is received from the VAP 103, it will send a TCAP(AIN Disconnect) message to the LDS 104 if not sent already, and thecall will be disconnected without any announcement.

XV. Call Forwarding

A. Unconditional Call Forwarding

A user of the MS 101 may not always have the MS 101 with him or her. Itmay be useful in such a situation to allow for incoming calls to the MS101 to be forwarded to another predetermined DN or DNs. This DN to whichcalls are forwarded is referred to herein as the FwdDN. Various types ofcall forwarding are available in the WCS 140. For example, calls may beforwarded unconditionally, such that a call to a DN that would otherwisebe destined for the MS 101 associated with the DN would be forwardedinstead to a predetermined FwdDN. This unconditional call forwardingfeature may alert both the MS 101 and the communication device at theFwdDN, or only the communication device at the FwdDN such that the MS101 is not alerted at all.

To activate this “unconditional call forwarding” feature, the MS 101user may dial a feature activation code such as *90#[FwdDN], followed bythe SEND button on the MS 101. In this example, “*90” indicates theunconditional call forwarding feature. The phrase FwdDN in the brackets“[ ]” represents the intended DN to which a call should be forwarded(the brackets themselves are not actually dialed in this example). Todeactivate the unconditional call forwarding feature, the MS 101 usermay enter a sequence such as *900 (or other appropriate sequence)followed by the send button.

FIG. 26 is an exemplary flow chart of how the unconditional callforwarding feature may work. A call may be made directed to the MS 101subscriber's DN (step 2601). A determination is made whether theunconditional call forwarding feature has been activated for the MS 101(step 2602). If so, then FwdDN is determined (step 2603) and the call isautomatically forwarded to FwdDN (step 2604). If the unconditional callforwarding feature has not been activated for the MS 101, then the callis routed to the MS 101 and/or further processing is performed on thecall.

An exemplary embodiment of how the above steps for unconditional callforwarding may be performed is now described with reference to FIG. 27.Once the unconditional call forwarding feature has been activated for anMS 101, a PSTN 125 or WCS 140 user may dial the called WCS 140subscriber's DN. Responsive to the LDS 104 receiving the incoming callfor the WCS 140 subscriber at DN (the call is assumed in this example tobe initiated from the PSTN 125) (step 2701), a TCAP AIN TAT message maybe sent from the LDS 104 to the NSP 106 (step 2703). Upon receipt of theTCAP AIN TAT message, the NSP 106 may check the feature activation tablefor the MS 101 and may determine that the MS 101 has activated theunconditional call forwarding feature. The NSP 106 may further check thesubscriber profile and find that the unconditional call forwardingfeature is active for the called MS 101. If the unconditional callforwarding feature is active, the NSP 106 may retrieve the callforwarding number (FwdDN). The NSP 106 may immediately use the FwdDN asthe forwarding number and may send a TCAP (AIN Forward_Call) message tothe LDS 104 (step 2705). The LDS 104 may then assume the call processingand forward the call to FwdDN (step 2707).

B. Programmable Ring Call Forwarding

Call forwarding may alternatively or additionally be configured toforward a call in response to a selected number of rings occurring atthe called MS 101 and/or the passage of a certain amount of time. Forexample, a call may be forwarded to FwdDN after three seconds havepassed (e.g., after three seconds of alerting time at the MS 101). Asanother example, the call may be forwarded after eight seconds havepassed.

To activate this “programmable ring call forwarding” feature, the MS 101user may dial a feature activation code such as *91*4#[FwdDN], followedby the SEND button on the MS 101. Such a command may indicate that callsshould be forwarded to FwdDN after four seconds. In this example, “*91”indicates the programmable ring call forwarding feature, and the “4”after the star sign indicates either the number of seconds or the numberof rings after which a call should be forwarded, depending upon how theWCS 140 is configured. This number may be in the range of, e.g., 0 to 30seconds, or 0 to 10 rings, changeable through the WCS 140 OA&Minterface. To deactivate the programmable ring call forwarding feature,the MS 101 user may enter a sequence such as *910 followed by the sendbutton. If no amount of time is specified by the user (e.g., by dialing*91#[FwdDN]) or the amount of time entered is out of range, then adefault amount of time, such as four seconds, may be used.

FIG. 32 is an exemplary flow chart of how the programmable ring callforwarding feature may work. Referring to the same call as in FIGS. 26,28, and 30, and if the call has not yet been forwarded to FwdDN, adetermination is made whether the programmable ring call forwardingfeature has been activated for the MS 101 (step 3201). If this featurehas not been activated, then the MS 101 is alerted to the call (e.g. byringing the MS 101) and the call routed to the MS 101 upon answering(step 3202) and/or further processing is performed on the call. If theprogrammable ring call forwarding feature has been activated for the MS101, then a time-out period is determined (step 3203). The time-outperiod may either be predetermined by the subscriber or set to a defaultvalue. The MS 101 is also alerted to the existence of the call, and atimer for timing the time-out period is started (step 3204). It isdetermined whether the call has been answered at the MS 101 before thetimer has finished (step 3205), and if so, then the call is routed tothe MS (step 3206). If the call has not been answered within theallotted time, then FwdDN is determined (3207) and the call is forwardedto FwdDN (step 3208).

An exemplary embodiment of how the above steps for programmable ringcall forwarding may be performed is now described with reference to FIG.33. Once the programmable ring call forwarding feature has beenactivated for the MS 101, an incoming call to the subscriber's DN isautomatically forwarded to the FwdDN after the selected amount of timeor number of rings. A PSTN 125 or WCS 140 user may dial the WCS 140subscriber's DN (i.e., the subscriber who has activated the programmablering call forwarding feature). The LDS 104 may receive the ISUP IAMmessage associated with the call (the call is assumed in this example tobe initiated from the PSTN 125) (step 3301). In the present embodiment,the LDS 104 may determine that the dialed DN is provisioned for AINTermination Attempt Trigger (TAT). Responsive to such a determination,the LDS 104 may suspend delivery of the call and may send an AIN querymessage to the NSP 106 (step 3303) for an appropriate routinginstruction.

When the NSP 106 receives the AIN TAT message, the NSP 106 may find thatthe subscriber's MS 101 is active and idle in its serving area. The NSP106 may then page the MS 101 through the VAP 103 (steps 3305, 3307)using IS-136 paging procedures, and may also start a TT6 timer 3308. Aspart of the page request message in step 3305, the NSP 106 may send theMSID that the VAP 103 will use to complete the incoming call setupprocedure. When the MS 101 responds to the page (steps 3309, 3311), theVAP 103 may forward the page response in the form of a Page Responsemessage, which includes the Forward Directory Number (FDN), to the NSP106 (step 3313). The VAP 103 may also start an event timer TT5 3314 atthis time to prevent permanent holding of RF and ISDN B-channelresources.

If the TT6 timer 3308 expires and the NSP 106 has not received the PageResponse message in step 3313, the NSP 106 may authorize calltermination to the DN. On the other hand, if the NSP 106 receives thePage Response message before the TT6 timer 3308 expires, the NSP 106 maycancel the TT6 timer 3308 and determine that the current VAP 103 has theresources to serve the incoming call. The NSP 106 may also check whetherthe programmable ring call forwarding feature is active for theparticular MS 101. The NSP 106 gets the TFPR value, which signifies thetime period for which the MS 101 should ring before the call should beforwarded, from the subscriber profile. At this point, the NSP 106 maydirect (using a TCAP Conversation package) the LDS 104 to forward thecall to the FDN of the VAP 103 serving the MS 101 (step 3315). The TCAPConversation package may include the T(NoAnswer) timer value in the TCAPAIN message to indicate the length of the ringing after which the callshall be forwarded. The message may be in the form of TCAP (AINForward_Call[FDN], NEL[O_No_Answer], T(NoAnswer)), where T(NoAnswer) isset to be the time after which the call should be forwarded. Forexample, where the user activated the programmable ring call forwardingfeature as *91*5#[FwdDN], then T(NoAnswer) would be set to five seconds.

The LDS 104 may start the T(NoAnswer) timer 3318 for the FDN and send aQ.931 Setup message to the VAP 103 (step 3317). Upon receipt of theQ.931 Setup message, the VAP 103 may cancel the TT5 timer 3314, initiateDTC designation to the MS 101 (step 3319), start a TT2 timer 3320, andsend a Q.931 Call Proceeding message to the LDS 104 (step 3321).

At this point, the MS 101 may tune to the traffic channel. When the VAP103 detects that the MS 101 is on the traffic channel via a DVCC statuschange (step 3323), the MS 101 may cut through the ISDN/B-Channel andinitiate the Alerting procedures to both the call legs (i.e., in boththe LDS 104 and MS 101 directions). The VAP 103 may send an IS-136Alert-With-Info message to the MS 101 (step 3325) and wait for an IS-136Mobile ACK message from the MS 101 (step 3351). When the VAP 103receives the Mobile ACK message, the VAP 103 may start a TT4 timer 3326and send a Q.931 Alerting message to the LDS 104 (step 3327). Uponreceipt of the Q.931 Alerting message, the LDS 104 may send an ISUP ACMmessage to the switch in the PSTN 125 (step 3329) and generate aring-back tone towards the calling party (step 3331).

When the T(NoAnswer) timer 3318 expires on the LDS 104, the LDS 104 maysend an event notification to the NSP 106 (step 3333) in the form of anAIN O_No_Answer trigger. Upon receipt of the AIN O_No_Answer trigger,the NSP 106 may check if the programmable ring call forwarding featureis active for the MS 101. If the feature is active, the NSP 106 may getthe call forwarding number from the subscriber profile and direct theLDS 104 to forward the call to the call forwarding number (FwdDN) (step3335) using a TCAP (AIN Forward_Call[FwdDN]) message. The LDS 104 maythen release the ISDN-B channel setup by sending a Q.931 Disconnectmessage to the VAP 103 (step 3337).

In response to the Q.931 Disconnect Message, the VAP 103 may send aQ.931 Release message to the LDS 104 (step 3339). In response, the LDS104 may send a Q.931 Release Complete message to the VAP 103 (step3341). The VAP 103 may release the RF resources by sending an IS-136Release message to the MS 101 (step 3343), and may send a TerminationResult [fail] message to the NSP 106 (step 3345). The MS 101 may send anIS-136 Mobile ACK message to the VAP 103 (step 3347). At this point,call processing may be assumed by the LDS 104 and the call will beforwarded to FwdDN (step 3349).

If the call is answered at the MS 101 before the T(NoAnswer) timer 3318expires, or if the programmable ring call forwarding feature is notactivated for the MS 101, then the call will be processed normallywithout the call being forwarded (unless another call forwarding featureas described herein is activated for the MS 101).

C. Bust Call Forwarding

Call forwarding may alternatively or additionally be configured toforward a call depending upon whether the subscriber's MS 101 is busy(i.e., currently handling a call). For example, incoming calls to thesubscriber's DN may be routed to the subscriber's MS 101 when it is notbusy, and forwarded to FwdDN when the MS 101 is busy.

To activate this “busy call forwarding” feature, the MS 101 user maydial a feature activation code such as *93#[FwdDN], followed by the SENDbutton on the MS 101. In this example, “*93” indicates the busy callforwarding feature. To deactivate the busy call forwarding feature, theMS 101 user may dial, e.g., *930 and then the SEND button.

FIG. 28 is an exemplary flow chart of how the busy call forwardingfeature may work. Referring to the same call as in FIG. 26, and if thecall has not yet been forwarded to FwdDN, a determination is madewhether the busy call forwarding feature has been activated for the MS101 (step 2801). If so, it is then determined whether the MS 101 is busy(step 2802). If the busy call forwarding feature is active and the MS101 is busy, then FwdDN is determined (step 2803) and the call isautomatically forwarded to FwdDN (step 2804). If the busy callforwarding feature has not been activated for the MS 101 and/or the MSis not busy, then the call is routed to the MS 101 and/or furtherprocessing is performed on the call.

An exemplary embodiment of how the above steps for busy call forwardingmay be performed is now described with reference to FIG. 29. Once thebusy call forwarding feature has been activated for the MS 101, anincoming call will be automatically forwarded to FwdDN if the MS 101 isbusy. When the LDS 104 receives an incoming call for the WCS 140 user(DN) (step 2901), the LDS 104 may send a TCAP AIN TAT message to the NSP106 (step 2903). Upon receipt of the TCAP AIN TAT message, the NSP 106may check the feature activation table for the MS 101 and determinewhether the MS 101 has activated the busy call forwarding feature. TheNSP 106 may also determine whether the MS 101 is currently busy. If theMS 101 is currently busy (e.g., busy due to call 2901) and the busy callforwarding feature is activated for the MS 101, the NSP 106 may use theFwdDN as the forwarding number and send a TCAP (AIN Forward_Call)message to the LDS 104 (step 2905). The LDS 104 may then assume callprocessing and forward the call to FwdDN (step 2907). If the MS 101 isnot currently busy, or if the busy call forwarding feature is notactivated for the MS 101, then the call will be processed normallywithout being forwarded (unless another call forwarding feature asdescribed herein is activated for the MS 101).

D. Time-of-day Call Forwarding

Call forwarding may alternatively or additionally be configured toforward a call depending upon the time of day, day of week, and/or date.For example, a call may be forwarded to FwdDN on weekends but not onweekdays. As another example, incoming calls to a particularsubscriber's DN may be forwarded to a first FwdDN between begin time9:00 a.m. and end time 6:00 p.m., to a second different FwdDN betweenbegin time 6:00 p.m. and end time 8:00 p.m., and not forwarded at allother times (i.e., routed to subscriber's normal MS 101 at all othertimes).

To activate this “time-of-day call forwarding” feature, the MS 101 usermay dial a feature activation code such as*92*[BeginTime]*[EndTime]#[FwdDN], followed by the SEND button on the MS101. In this example, “*92” indicates the time of day call forwardingfeature. “[BeginTime]” indicates the selected begin time, and“[EndTime]” indicates the selected end time. The begin and end times maybe entered in any format. For example, the format may be a 24-hourmilitary time format, such that if the chosen begin time is 8:30 a.m.,and the chosen end time is 6:00 p.m., then BeginTime would be entered bythe subscriber as 0830 and EndTime would be entered as 1800. Todeactivate the time-of-day call forwarding feature, the MS 101 user maydial, e.g., *920 and then the SEND button.

FIG. 30 is an exemplary flow chart of how the time-of-day callforwarding feature may work. Referring to the same call as in FIGS. 26and 28, and if the call has not yet been forwarded to FwdDN, adetermination is made whether the time-of-day call forwarding featurehas been activated for the MS 101 (step 3001). If so, it is thendetermined whether the current time is between predetermined begin andend times (step 3002). If the time-of-day call forwarding feature isactive and the current time is between the begin and end times, thenFwdDN is determined (step 3003) and the call is automatically forwardedto FwdDN (step 3004). If the time-of-day call forwarding feature has notbeen activated for the MS 101 and/or the current time is not between thebegin and end times, then the call is routed to the MS 101 and/orfurther processing is performed on the call.

An exemplary embodiment of how the above steps for time-of-day callforwarding may be performed is now described with reference to FIG. 31.Once the time-of-day call forwarding feature has been activated for theMS 101, an incoming call to the subscriber's DN is automaticallyforwarded to FwdDN depending upon the time, data and/or day. When theLDS 104 receives an incoming call for the WCS 140 user (DN) (step 3101),the LDS 104 may send a TCAP AIN TAT message to the NSP 106 (step 3103).Upon receipt of the TCAP AIN TAT message, the NSP 106 may check thefeature activation table for the MS 101 and determine that the MS 101has activated the time-of-day call forwarding feature. The NSP 106 maycheck a clock (such as the internal clock of the NSP 106) and comparethe clock with the user-programmed time period(s). For example, the NSP106 may check whether the current time as indicated by the clock isbetween the begin time and the end time of each user-programmed timeperiod.

If the clock is within one of the user-programmed time periods, the NSP106 may use FwdDN as the forwarding number and send a TCAP (AINForward_Call) message to the LDS 104 (step 3105). The LDS 104 may thenassume call processing and the call is forwarded to FwdDN (step 3107).If the current time as indicated by the clock is not within one of theuser-programmed time periods, or if the time-of-day feature is notactivated for the MS 101, then the NSP 106 may treat the incoming callas a normal incoming call, such that the incoming call will not beforwarded (unless another call forwarding feature as described herein isactivated for the MS 101).

Any or all of the above-described features may be activated,deactivated, and/or otherwise configured in any combination orsubcombination desired for a particular MS 101. For example, callforwarding for a particular MS 101 may be configured so as tounconditionally forward calls on weekends, and to forward calls onlyafter six seconds on weekdays. Such activation, deactivation, and/orother configuration of the features may be controlled by the user viathe MS 101, via a telephone call to the service provider (e.g., acustomer service representative), via the Internet, and/or via anintranet or other private or public network coupled to the WCS 140.Alternatively, the WCS 140 may be configured such that only one callforwarding feature at a time may be activated for a particular MS 101.In such an embodiment, if a call forwarding feature is activated whilean existing call is forwarding feature is already activated for the MS101, the new call forwarding feature may replace the existing callforwarding feature.

FIG. 34 illustrates a display of an exemplary interactive Internet webpage 3400 for activating, deactivating, and/or configuring featuresdescribed herein. The web page 3400 may allow a user to define one ormore FwdDNs to which calls should be forwarded depending upon one ormore conditions. An advantage to using an Internet web page to activate,deactivate, and/or configure features is that the user may see theentire configuration on one display. This may be important if the userhas selected a particularly complex feature configuration. When theInternet is used to configure call forwarding features or otherfeatures, a server that runs the web page 3400 may be coupled to the WCS140.

The web page 3400 shown in FIG. 34 includes one or more forwarded numbertext boxes 3401 within which a user can enter selected FwdDNs, checkboxes 3402 for selecting whether a call should be unconditionallyforwarded to a particular FwdDN, text boxes 3403 for selecting how manyrings should occur at the MS 101 (and/or how much time to wait) beforeforwarding a call for a particular FwdDN, check boxes 3404 for selectingwhether a call should be forwarded to a particular FwdDN when the MS 101is busy, and text boxes 3405 for selecting time ranges within which acall should be forwarded to a particular FwdDN. Of course, the web page3400 may include any type of text box, check box, pull-down menu, scrollbox, etc., any of which may be used interchangeably as desired with anyof the text boxes and/or check boxes 3401-3405. What is important isthat the web page 3400 allows the user to configure the call forwardingfeatures and/or other calling features for his/her MS 101.

For example, as shown in FIG. 34, call forwarding for an MS 101 having aDN 123-123-4567 may be configured on the web page 3400 tounconditionally forward all incoming calls, but only on weekends, toFwdDN 123-456-7890. Call forwarding for the same MS 101 may further beconfigured to forward incoming calls after three rings at the MS 101,but only on Mondays between 8:00 a.m. and 6:00 p.m., to FwdDN234-567-8901. Call forwarding for the same MS 101 may further beconfigured to forward incoming calls after two rings at the MS 101 orwhen the MS 101 is busy, but only on Oct. 26, 1999, to FwdDN345-678-9012. Thus, a particular MS 101 may have multiple callforwarding and/or other features simultaneously configured. If there isa conflict in features (e.g., unconditional call forwarding at all timesin combination with call forwarding only when busy at all times), thenthe web page 3400 may indicate to the user that such a conflict existsand that the features should be re-configured accordingly.

XVI. Call Waiting

FIG. 35 provides an exemplary call flow diagram for implementing thecall waiting feature according to an illustrative embodiment of thepresent invention.

For purposes of this discussion, it will be assumed that there exists anactive call 3502 between a mobile station MS 101A and a party coupled tothe PSTN 125. The call 3502 in progress is referred to by the VAP 103Aand the NSP 106 as having a call reference value, CR=1, and a B ChannelID (Ch ID=B1). When a second call originating from within the PSTN 125is made to a DN of a party in a WCS system, such as a party using MS101A, an ISUP LAM [DN] message 3504 is received by the LDS 104. The LDS104 processes the ISUP LAM message 3504 and discovers that the calledparty's DN is provisioned for AIN call treatment. Then, the LDS 104sends an AIN query message, TCAP (AIN Termination Attempt [DN]) message3506, to the NSP 106 for an appropriate routing instruction. Responsiveto the AIN query message and knowing that the MS 101A is involved in anactive call 3502, the NSP 106 determines if the MS 101A subscribes tothe call waiting feature by checking the WCSD (Wireless Centrex SystemDatabase) and determines if the call waiting feature is currentlyavailable and has been activated by the subscriber.

If the MS 101A does not subscribe to the call waiting feature or thefeature is not presently available such as by being deactivated, the NSP106 sends a TCAP message (not shown) to the LDS 104 with Authorize Term(authorize termination) message to the original DN. The call waitingfeature may not be available due to manual or automatic deactivation.According to one embodiment of the invention, the user may manuallydeactivate the call waiting feature when they do not want to beinterrupted by, for example, pressing a special key code on theirhandset prior to making a call. Also, the call waiting feature may beautomatically deactivated in a number of instances, such as: 1) when theMS is already engaged in a conference call; 2) when the MS is alreadyengaged in another call waiting; 3) when the MS has received anautomatic callback call with another call on hold; and 4) aspredetermined by the subscriber including based on the physical locationof the MS, the time of day, or the other party on the original call.When the LDS 104 receives the Authorize Tenm message, the incoming callmay be connected to the DN (desktop phone) or coupled to the VMS 107 forfurther handling.

If the MS 101 A subscribes to the call waiting feature and it ispresently available or active, then the NSP 106 sends an AIN ForwardCall message in a TCAP conversation package 3508 to the LDS 104. TheTCAP conversation package 3508 directs the LDS 104 to forward the callto the FDN (forward directory number). The FDN is the DN in the VAP 103Athat is used to deliver the call to the MS 101A. The LDS 104 then sendsa Q.931 Setup message 3510 including the FDN, a call reference value(CR=2) and a second B Channel ID (Ch ID =B2) to the VAP 103A and startsa No Answer Timer (T(NoAnswer)). The VAP 103A responds to the Q.931Setup message 3510 by sending a Q.931 Call Proceeding message 3512.

Next, the VAP 103A sends the NSP 106 a Call Waiting Proceeding message3520 including the MSID and FDN and starts the TCW1 timer (first callwaiting timer). In response, the NSP 106 sends a Play Voice Promptmessage 3522 including a call waiting tone to the VAP 103A and startsthe TCW2 timer (second call waiting timer). Upon receipt of the PlayVoice Prompt message 3522, the VAP 103A cancels the TCW1 timer andgenerates and plays the call waiting (CW) tone 3524 to the user of MS101A. The tone may be generated and played at a preset interval for apreset duration, such as every five seconds for one minute.

While the CW tone 3524 is being generated, the VAP 103A sends a Q.931alerting message 3514 to the LDS 104. The LDS 104 responsive to theQ.931 alerting message 3514 sends an ISUP ACM message 3516 to the switchin PSTN 125. In the meantime, the LDS 104 sends a ring back tone 3518 tothe PSTN 125 caller.

The user of MS 101A may choose to answer the incoming call by sending amessage to the VAP 103A before T(NoAnswer) expires. According to anillustrative embodiment of the invention, the user can answer theincoming call and place the existing call on hold by pressing the “send”button, which in turn sends an IS-136 Flash with Info message 3526 tothe VAP 103A. In response, the VAP 103A sends a Feature Request [Flashwith Info] message 3528 to the NSP 106 and starts the TCW3 (third callwaiting timer). Also, the VAP 103A sends an IS-136 Flash with Info ACKmessage 3530 to the MS 101A acknowledging receipt of the Flash with Infomessage 3526. When the NSP 106 receives the Feature Request [Flash withInfo] message 3528, it cancels the TCW2 timer and sends a FeatureRequest ACK [Hold and Answer Call Waiting] message 3532 to the VAP 103Aand starts the TCW4 timer (fourth call waiting timer). Next, the VAP103A cancels the TCW3 timer and initiates the Q.932 call hold procedurefor the existing call (CR=1) by sending a Q.932 Hold [CR=1] message 3534to the LDS 104. The LDS then responds by sending a Q.932 Hold ACK [CR=1]message 3536 to the VAP 103A to acknowledge that the current call isheld, Call Held (CR=1) 3538.

The VAP 103A sends a Q.931 Connect [CR=2] message 3540 to LDS 104 tocause initiate connection of the incoming call (CR=2). The LDS 104 thencancels the T(NoAnswer) timer and sends an ISUP ANM message 3542 to PSTN125 switch to cut through the voice path 3548. After the LDS 104 sendsan ISDN Q.931 Connect ACK message 3544 to the VAP 103A for the incomingcall, it sends a TCAP (AIN Close) message 3550 to the NSP 106.Meanwhile, the VAP 103A sends a Hold & Answer Call Waiting Result[success] message 3546 to the NSP 106 indicating that the call waitingprocess has been successful. Then, the NSP 106 cancels the TCW4 timerand the voice path 3548 is established for the incoming call while theoriginal call (CR=1)is placed on hold. The voice path 3548 has a callreference value of CR=2 and a B Channel ID, Ch ID=B2.

It should be understood that the MS user could proactively handle thesecond call as described in other portions of this application inconjunction with the call waiting feature. Also, the user may switchback and forth between the second call (CR=2) and the original call(CR=1) in a number of ways. For example, the user may press the “send”button and reinstate the process described in FIG. 35 beginning withsending IS-136 Flash with Info message 3526 as set forth above.

FIG. 36 provides an illustrative flow diagram for implementation of thecall waiting feature according another embodiment to the presentinvention in which much of the intelligence is distributed to the VAP103A rather than in the NSP 106.

In step S361, an existing call (CR=1) between a PSTN user and MS 101A isin progress and a new call arrives for the MS 101A. Next, in step S362,the NSP 106 determines whether the call waiting feature is available forthe MS 101A. If the NSP 106 determines that call waiting is notavailable, then the NSP 106 informs the LDS 104 that the MS 101A is busyin step S363 and a busy signal can be returned to the PSTN user, oranother call routing procedure may be implemented such as routing thecall for further handling as described elsewhere in the application,such as to the desktop phone associated with the MS 101A or the VMS 107.Alternatively, if the NSP 106 validates that call waiting is available,then, in step S364, the NSP 106 instructs the VAP 103A to initiate thecall waiting procedure and the LDS 104 to forward the call to the VAP103A.

In step S365, it is determined whether the call (CR=2) has beenestablished successfully to the VAP 103A and the MS 101A. If the callhas not been established successfully in step S365, then, in step S366,the VAP 103A cancels the call waiting procedure and informs the NSP 106of the cancellation, which causes the NSP 106 to initiate the callrelease procedure. If the call has been established successfully, theLDS generates a ringback tone to the calling party and the VAP 103Asends a call waiting signal to the MS 101A and waits for a responsethereto in step S367.

The VAP 103A waits a predetermined period of time for a response fromthe MS 101A user in step S368. If the VAP 103A timer expires in stepS368, the VAP 103A informs the NSP 106 to release the call (CR=2) instep S369 similarly to step S366. However, if the MS 101A respondswithin the time period, the VAP 103A initiates the call hold procedurein which the LDS 104 places the original call (CR=1) on hold and theincoming call (CR=2) is established between the PSTN user and the MS101A in step S370. Also, in step S360, the VAP 103A informs the NSP 106of the successful call waiting result. In step S371, the MS 101A usermay toggle back and forth between the new call (CR=2) and the originalcall (CR=1) putting one on hold while communicating in the other.

XVII. Distinctive Ringing

The distinctive ringing feature allows a subscriber to be alerted by adistinctive indication, e.g., a ring, of an incoming call originatedfrom a communications unit assigned a specific directory number (DN). Asubscriber can provision one or more DNs that cause a distinctive ringto occur when a communications unit assigned a provisioned DN initiatesa call to the subscriber.

There are several ways a subscriber can provision the distinctiveringing DN list. For example, the user may access the Internet or aweb-based interface such as a WCS web site and input and update the DNlist. Also, the subscriber may contact a customer care centerrepresentative by phone and verbally communicate the numbers through anytype of communications unit (e.g., cell phone, landline phone, wirelesspalm top computer phone, etc.). Alternatively, a user may be directedthrough an automated phone menu to input the numbers by use of acommunications unit keypad or voice recognition system.

According to one embodiment, the user may provision the distinctiveringing services through the WCS system. In this regard, the subscribermay activate the feature by entering a feature activation code followedby a DN (e.g., *70#5555151) into the keypad of MS 101A and then pressingthe “send” button. Actuation of the “send” button sends the featureactivation message to the WCS system (e.g., NSP 106). The WCS systemthen may acknowledge activation of the feature and phone number by, forexample, returning a short message to the MS 101A. In addition, amessage indicating that a call origination request has been rejected maycontain feature activation/deactivation status information to bedisplayed to the user.

In a further modification, a subscriber can select a specificdistinctive ring for each DN from a plurality of available rings (e.g.,5 ring tones). For example, a subscriber may identify personal calls byone distinctive ring type (e.g., ring type 1), business calls by anotherdistinctive ring type (ring type 2), and a very important call by yetanother ring type (ring type 3). Also, the subscriber may define adistinctive ring for all calls originating from parties who have blockedtheir number pursuant to call blocking. Thus, the subscriber might sendthe feature activation code followed by the ring type and the DN (e.g.,*70#2#5555151) to the WCS system. When the subscriber fails to enter aring type, a default distinctive ring (e.g., ring type 1) can beassigned to the DN.

To remove a phone number from the DN list, the subscriber, in additionto the methods note above, may enter a feature deactivation codefollowed by the DN (e.g., *700#DN) and press the “send” button. Also,the subscriber may deactivate the distinctive ringing for all numbers byentering a feature deactivation code (e.g., *700#*) and the “send”button on the MS 101A. A more detailed discussion of feature activationand deactivation is provided at other places in the instant description,for example at section IX.

According to an illustrative embodiment of the invention, the DN listmay be stored in a memory in the NSP 106 or a memory location accessibleto the NSP 106. The DN list may include any amount of numbers dependingon the capacity of the memory employed. In one embodiment, up to thirtynumbers may be preset for distinctive ringing. In this embodiment, if asubscriber attempts to provision a thirty-first number, the system mayreject the provision or alternatively overwrite the first numberprovisioned (a first-in-first-out (FIFO) scheme). Also, the size of thephone number in the list can be set according to the capacity of thememory. In an illustrative embodiment, the size of the numbers in thelist may range from four to fifteen digits. Also, it should beunderstood that a DN of a calling party outside or inside the WCSenvironment may be defined to have a distinctive ring.

FIG. 37 provides an exemplary call flow diagram for implementing thedistinctive ringing feature according to an illustrative embodiment ofthe present invention. While the IS-136 standard is used to illustrateone implementation of the present invention, it should be understoodthat the present invention is applicable to other cellular or PCSsystems.

When a user of the PSTN 125 dials the DN of a WCS subscriber, the LDS104 receives an ISUP LAM message 3702 from the PSTN 125. If the dialedDN is provisioned for AIN Termination Attempt Trigger (TAT), the LDS 104suspends the delivery of the call and sends an AIN query message 3704(i.e., TCAP (AIN Termination_Attempt [DN])) to the NSP 106 for anappropriate routing instruction.

The NSP 106 upon receipt of the AIN query message 3704 determines if theDN of the calling party is a number for which distinctive ringing isdesired (i.e., a DR_DN). For example, the NSP compares the DN of thecalling party with each DR_DN in the distinctive ringing list for the MS101A (e.g., in the wireless centrex system database (WCSD) entry for theMIN of MS 101A). If the DN of the calling party matches a DR_DN. in thedistinctive ringing list, the NSP 106 retrieves the informationregarding the distinctive ring from its storage location and specifiesin the “signal” portion of a page request message 3706 that adistinctive ring should be provided for the MS 101A. Also, if multipledistinctive ring tones are available, the NSP 106 indicates the specificdistinctive ring tone for reception by the MS 101A in the “signal”portion of the page request message 3706. Assuming the subscriber's MS101A is active in the service area of the NSP 106, the NSP 106 sends thepage request message 3706 (i.e., Page Request [MSID, signal]) to the VAP103A serving MS 101A.

When the NSP sends the page request message 3706 to the VAP 103A, atimer TDR1 starts. Responsive to the page request message 3706, the VAP103A sends an IS-136 Page message 3708 to the MS 101A. If the MS 101Adoes not respond to the IS-136 page message 3708 before timer TDR1expires, then the call is terminated in another manner by transfer tothe VMS, user's desktop phone or otherwise as described herein.Otherwise, the MS 101A responds to the IS-136 page message 3708 via anIS-136 page response message 3710 sent to the VAP 103A. In turn, the VAP103A sends a page response message 3712 (i.e., Page Response [FDN] tothe NSP 106.

After receiving the page response message 3712, the NSP 106 directs LDS104 to forward the call to the Forward Directory Number (FDN) of the VAP103A serving the MS 101A in a TCAP conversation package 3714, TCAP (AINForward_Call [FDN], NEL [O_No_Answer]). The NSP 106 also indicates itsinterest in event (O_No_Answer for FDN) by sending next event list NEL[O_No_Answer]) information to the LDS 104 in a request component thataccompanies the routing component in the TCAP conversation package 3714.The LDS 104 then starts a No Answer Timer TT10 for the FDN. Also, LDS104 sends a Q.931 setup [FDN] message 3716 to the VAP 103A.

The VAP 103A then sends an IS-136 digital traffic channel (DTC)designation message 3718 to the MS 101A. Also, VAP 103A sends a Q.931call proceeding message 3720 to the LDS 104. The MS 101A then tunes tothe digital traffic channel and responds to the VAP 103A with MS on DTCmessage 3722. The VAP 103A detects the MS 101A on the appropriatetraffic channel. Next, the VAP 103A alerts MS 101A with analert-with-info [signal] message 3724. The alert-with-info message 3724includes the appropriate distinctive ringing tone, if any, for play tothe subscriber of the MS 101A. The VAP 103A then sends a Q.931 alertingmessage 3726 to LDS 104. The MS 101A acknowledges receipt of thealert-with-info message 3724 by sending the VAP 103A an IS-136 mobileacknowledge (Mobile ACK) message 3728. Upon receiving the Q.931 alertingmessage 3726, the LDS 104 sends an ISUP ACM message 3730 to the switchin PSTN 125. Meanwhile, the LDS 104 sends a ringback tone 3732 to thecalling party from the PSTN 125.

When the MS 101A answers (before TT10 expires), it sends an IS-136connect message 3734 to the VAP 103A. The VAP 103A then sends Q.931connect message 3736 to the LDS 104 in response to the IS-136 connectmessage 3734 from MS 101A. The LDS 104 then cancels timer TT10 and sendsISUP ANM message 3738 to the PSTN 125 switch and cuts through the voicepath 3746. After the LDS. 104 sends a Q.931 connect ACK message 3740 tothe VAP 103A, it then sends TCAP (Completed) message 3742 to the NSP 106to complete the TCAP transaction. Responsive to Q.931 connect ACKmessage 3740, the VAP 103A sends termination result [Success] message3744 to the NSP 106 for billing and other OAM&P purposes. At this point,voice path 3746 has been established and the call proceeds between thecalling party from the PSTN 125 and the MS 101A subscriber.

XVIII. Returning Calls

Technologies that facilitate wireless communication are emerging at anever-faster rate. Such technologies are employed in end-user devicessuch as pagers, communication systems, and mail systems such as voicemail and email systems. In wireless communication systems, a need existsto provide a new service in the wireless environment that is analogousto the call return feature provided on wired telephone handsets. A usermay be unable to answer his wireless handset when a call is received.For example, the user may be in a meeting where the call would beperceived as a disruption, may be waiting for another call, may be busyon another call, or may not wish to interrupt whatever he is doing whenhe receives the incoming call.

In existing wireless handsets, a user may preset his wireless phone toavoid disruption of his activity when the incoming call arrives, but noprovision has been made to allow the user to automatically return thecall at a later, more convenient time. Thus, a user who is interruptedor busy cannot avoid answering the incoming call without one of: eithermissing the call entirely or having to manually redial a number saved onthe terminal or on a system that indicates the phone number of thecaller. Clearly, there is a need for a system, wireless apparatus andmethod for allowing a user the flexibility of automatically dialing backan incoming call in a wireless communication system.

The present invention provides a system, wireless apparatus and methodfor allowing a user the flexibility of automatically dialing back anincoming call in a wireless communication system at a time convenient tothe user that received the call, a functionality that is analogous tothe call return feature provided on wired telephone handsets. Forexample, a wireless phone may implement the present invention.

In the example below, implementation of the present invention isaccomplished using a wireless phone in a Wireless Centrex System 140(WCS). The WCS 140 provides a private wireless access system that isunconnected to any public macro-cellular system and providesCentrex-type services. FIG. 1B shows a block diagram of an illustrativearchitecture of a WCS platform wherein the present invention may beutilized. The WCS platform includes a local digital switch 104 (LDS), aremote digital terminal 102 (RDT, e.g., SLC-2000), a network serverplatform 106 (NSP), voice access ports 103A, 103B (VAP) and a pluralityof associated IS-136 digital time division multiple access (TDMA)cellular or personal communications service (PCS) mobile stations 101A,101B which implement the present invention. The LDS 104 is a TR-08 andGR-303 compatible local digital switch that employs distributedintelligence, process-oriented software, and coordinated autonomouscomputing elements to provide a flexible, modular, reliable and robustdigital switching system. The LDS 104 provides a single platform foradvanced services, including Integrated Services Digital Network (ISDN),Centrex, Custom Local Area Signaling Services (CLASS), custom calling,and Advanced Intelligent Network (AIN) capabilities. The LDS 104 alsosupports X.25 packet switched data communication and circuit switcheddata, and provides a gateway to local and long distance networks. Theswitching fabric, administration, message switching, and call switchingfunctions are provided by the LDS 104.

The AIN capabilities of the LDS 104 provide AIN switch software thatenables the network provider to create, deploy, and change services tomeet user's requests. The AIN software allows the LDS 104 to act as anAIN service switching point to communicate with service control pointsand intelligent peripherals. For example, the LDS 104 may be a 5ESSmanufactured by Lucent Technologies or a DMS-100 manufactured by Nortel.In the WCS configuration illustrated in FIG. 1A, the NSP 106 acts aservice control point, directing call processing on the LDS 104.

The RDT 104 is a digital loop carrier terminal that supports the plainold telephone system (POTS), ISDN, high-speed transport, and specialservices such as private lines and private branch exchange (PBX)services. For example, the RDT 102 may be implemented by a SLC2000manufactured by Lucent Technologies or an Access Node manufactured byNortel. The RDT 102 interfaces, typically at a central office, with theLDS 104. The RDT 102 provides the distribution of service interfacesbetween the LDS 104 and the user's premises, extending the digitalaccess network.

The NSP 106 provides VAP 103A, 103B control, including mobile stationand mobility management, call control, and feature applications. VAPs103A, 103B are micro-cellular base stations or radio ports that supportthe IS-136 air interface with IS-136 mobile stations such as digitalTDMA cellular/PCS (personal communications services) units 101A, 101B.The VAPs 103A, 103B support plug-and-play operations by connecting tothe RDT 102 via standard open interfaces such as the ISDN basic rateinterface (BRI) lines, typically using 2B+1D signaling protocol as isknown in the art.

The IS-136 air interface standard is the EIA/TIA Interim Standard, alsoknown as the North American or U.S. TDMA standard, that addressesdigital cellular and PCS systems employing time division multiple access(TDMA). The IS-136 standard was developed to provide very flexibletechnical, service and investment options for subscribers and operators.IS-136 specifies a DCCH (Digital Control Channel) to support newfeatures controlled by a digital signaling and control channel between acell site (e.g., radio base station) and terminal equipment (e.g.,mobile station). The IS-136 air interface between the VAPs 103A, 103Band the mobile stations 101A, 101B can support voice and messagingapplications. The mobile stations 101A, 101B may be, but are not limitedto, a terminal or a typical wireless phone having a keypad, displayscreen, and an alarm generator for generating a ringing or tone sound.

The present invention is implemented in the above system by cellular orpersonal communications service (PCS) mobile stations 101A, 101B.

FIG. 1B also includes POTS 108 and ISDN 109, which may be utilized asdescribed above. The WCS offers a wireless access system with Centrex toprovide voice access and may either supplement existing wired Centrexservice with wireless access or provide wireless-only stand-alonetelecommunications services. WCS can connect the NSP 106 to amacro-cellular network to support integrated mobility functionsincluding terminal handoff and personal roaming features. The WCSprovides location and mobility management for a WCS's subscriber mobilestation 101A, 101B inside the WCS service area. Cordless communicationmay be provided anywhere, anytime in the WCS service area.

FIG. 38 is a signal flow chart showing signaling flow steps for anillustrative embodiment implementing a call return in accordance withthe present invention. FIG. 38 shows the call flow when the userjustrequests to return the last incoming call. To facilitate understanding,the steps are partitioned into two general areas: a and b.

Section (a) of FIG. 38 shows how to display the called number to theuser. The user dials a predetermined feature access code, e.g., *69, andpresses the “send” button. An origination message, and optionally aserial number message, is sent by a mobile station MS 101A, 101B on aR-DCCH to a VAP 103A, 103B in accordance with the IS-136 standard.

The VAP receives the origination message and sends an originationrequest, for example, where the dialed digit is *69, to the NSP(point 1) and starts a first timer TO1. The NSP receives the originationrequest message, identifies that the message is a feature request andutilizes the ID of the MS 101A, 101B to check whether the MS 101A, 101Bis a valid, registered subscriber for the call return feature request.If the MS 101A, 101B is authorized for the call return feature, the NSPretrieves the digits of the last calling party number or directorynumber for returning the call (CallRet N) for the MS 101A, 101B andsends an origination ACK message (point 2→point 3) with the displayparameter that includes the CallReturnDN to the VAP and starts the timerTCR1. The TCR1 timer is set to a predetermined time that permits Q.931call processing, i.e., if this time was exceeded, the call would beterminated.

The VAP 103A, 103B stops the TOI timer and sends a Q.931 call setupsignal to the LDS 104. The LDS 104 sends an ISUP LAM signal to thePSTN/POTS 108 and may display the number on the MS's screen inaccordance with the display function set forth in the IS-136 standard.However, if the VAP 103A, 103B has not received the origination ACK fromthe NSP 106(point 3) before the expiration of the predetermined timethat will allow pre-processing of the feature request, the VAP 103A,103B will stop the TO1 timer and clear the origination request record.

Next, as shown in (b), the VAP 103A, 103B sends a Q.931 Setup signal tothe LDS 104. Then the originating switch, the LDS 104, sends an ISDNUser Part Initial Address Message (ISUP LAM) to the destination switchof the public switched telephone network (PSTN/POTS 108) to reserve anidle trunk circuit from the originating switch to the destinationswitch. Then, the LDS 104 sends a Q.931 Call Proceeding signal to theVAP 103A, 103B. The VAP 103A, 103B sends an IS-136 digital trafficcontrol (DTC) designation to the MS 101A, 101B. After the VAP 103A, 103Breceives a DTC signal from the MS 101A, 101B, the destination switch ofthe PSTN/POTS 108 sends an ISDN user part Address Complete Message (ISDNACM) to the originating switch, the LDS 104, to indicate that the remoteend of the trunk circuit has been reserved. Next, the LDS 104 sends aQ.931 alerting signal to the VAP 103A, 103B. The ringback tone isinitiated by the PSTN/POTS 108 over the trunk to the originating switch,the LDS 104. Then the PSTN/POTS 108 sends a ISDN User Part AnswerMessage (ISUP ANM) to the originating switch, the LDS 104, which thensends a Q.931 connect signal to the VAP 103A, 103B. The VAP 103A, 103Bthen sends a Q.931 connect acknowledgement signal to the LDS 104 and asignal indicating success via an origination result message to the NSP106. The NSP 106 stops timer TCR1, and a voice path is established.

Clearly the phone number for the incoming call must be known, e.g., notsecurity-protected for the feature of the present invention to function.Thus, when the phone number of the incoming call is unknown orsecurity-protected, the present invention may indicate that the phonenumber is unable to be displayed by a screen display, providing a voiceprompt, providing a predetermined tone, or the like.

ISDN User Part (ISUP) call signaling is utilized in the callpre-processing for implementing the feature of the present invention.ISUP defines the protocol and procedures that are used to set-up,manage, and release trunk circuits carrying data and voice alls over thepublic switched telephone network, PSTN. ISUP is used for ISDN andnon-SDN calls, but calls that originate and terminate at a same switchdo not use ISUP signaling. The ISUP message format includes informationcarried in the Signaling Information Field (SIF) which contains arouting label, a circuit identification code, and message type field.The ISUP Initial Address Message is sent in a “forward” direction byeach switch needed to complete the circuit between the LDS and thedestination switch of the PSTN until the circuit connects to thedestination switch. The ISUP Address Complete Message is sent in the“backward” direction to indicate that the remote end of the truckcircuit has been reserved. The originating switch then connects the MS101A, 101B to the trunk to complete the voice circuit. The destinationswitch generates a ringing tone. The MS 101A, 101B user hears theringing tone on the voice trunk. When the called party answers, thedestination switch terminates the ringing tone and sends the ISUP AnswerMessage to the originating switch. The ISUP message format depends onwhether the ANSI standard or the ITU-T standard is being implemented.

FIG. 39 illustrates one embodiment of steps for implementing a methodfor automatically returning an incoming call in a wireless communicationsystem in accordance with the present invention. The steps include:receiving 3902 the incoming call by a wireless apparatus andautomatically saving, where permitted, a phone number for the incomingcall; and initiating 3904, upon one of: a predetermined button/buttonsbeing pressed or a predetermined verbal call return command beingissued, automatic dialing of the phone number for the incoming call bythe wireless apparatus. Where desired, the method may further include,between the steps of receiving the incoming call and initiating dialingthe phone number for the incoming call, automatically displaying 3906the phone number of the incoming call on a display. Also, whereselected, where the phone number for the incoming call is unknown orsecurity-protected, the method may include indicating 3908 that thephone number for the incoming call is unable to be displayed. Indicatingthat the phone number for the incoming call is unknown or unavailable,for example, due to security protection, may be implemented by any knownmethod such as, for example, using a display, a voice prompt, or apredetermined tone. Where, after the step of receiving the incomingcall, at least one more incoming call is received, the method mayinclude automatically saving 3910 a phone number for each incoming call.Where selected, the method may also implement a step of automaticallydisplaying 3912 the phone number of a most recent incoming call, and/orallowing the user, at his convenience, to display the phone number of amost recent incoming call by manually pressing a predetermined button orbuttons 3914 or using a verbal command, thus conserving powerexpenditure for the display. Where selected, before initiating dialingthe phone number of the most recently received call, the user maydispose 3916 of a first displayed phone number by moving at least onefirst displayed phone number to an end of a list of phone numbers ofincoming calls received and/or may also transpose the first displayedphone number with a next phone number of the incoming calls received.Each of these two steps may be repeated as many times as desired.

As shown in FIG. 40, a wireless apparatus 4010 may be utilized forimplementing the method of the present invention in a wirelesscommunication system. Typically, the wireless apparatus 4010 is awireless phone or another handheld wireless communications device suchas, for example, a wireless digital assistant. The wireless apparatusincludes a memory 4002, for automatically saving, where permitted, aphone number for the incoming call received; and a wireless call returnprocessor 4004, coupled to the memory, for initiating, upon one of: apredetermined button buttons 4006 being pressed or a predeterminedverbal call return command being issued, automatic dialing of the phonenumber for the incoming call using the wireless apparatus. Whereselected, the memory may store other predetermined information. Forexample, a user profile may be downloaded to the memory to permitauthentication of the MS 101A, 101B at the VAP. Also, where a listing ofusage or billing record is downloaded from the NSP for updating at thebilling office, to avoid error, the billing record may be marked as “inuse” by the NSP until the updated billing record has been sent to theNSP. Alternatively, the time for the current usage may be accumulated inthe memory for a predetermined period and then forwarded to the NSP forincorporation into the user's billing record. The wireless apparatus mayfurther include a display 4008, coupled to the memory and the wirelesscall return processor, for automatically displaying, where permitted,the phone number of the incoming call on a display when the incomingcall is received. The display 4008 operates as described above.

As shown in FIG. 38, a wireless communication system may include awireless apparatus for automatically returning an incoming call. Thewireless communication system includes a switched communications network(for example, the PSTN 108), a NSP 106, a LDS 104, a VAP 103A, 103B, andat least one MS 101A, 101B. Each of the elements is arranged tocommunicate as described above.

Alternatively, as shown in FIG. 41, the method of the present inventionmay be described as utilizing the steps of: configuring 4102 a wirelesscommunication system to automatically return a previously received call;and returning 4104, automatically, the previously received call. Theconfiguration of the wireless communication system and the automaticreturn of the previously received call are accomplished as described forFIG. 38.

FIG. 42 is a block diagram of one embodiment of a wireless communicationplatform for providing automatic wireless call return in accordance withthe present invention. The platform includes: at least one mobilestation 4202 and a micro-cellular base station controller 4204. Amicro-cellular base station means a base station in which componentshave been miniaturized to a degree such that the base station ismountable on a pole, shelf, or a wall. The micro-cellular base stationcontroller 4204 is arranged to communicate wirelessly with the at leastone mobile station 4202 and to receive an incoming call directed to theat least one mobile station, for, when the at least one mobile station4202 is processing another call, automatically returning the incomingcall in accordance with a predetermined scheme to provide automatic callreturn for the at least one mobile station. The predetermined scheme isthe method described above. Where selected, the platform may furtherinclude a switching and database processor 4206 and a memory 4208. Theswitching and database processor 4206 is coupled to the micro-cellularbase station controller 4204 and a memory 4208 and is used for switchingthe incoming call according to the predetermined scheme to provide anautomatic call return for the at least one mobile station, upon one of:a predetermined button/buttons being pressed or a predetermined verbalcall return command being issued, by automatically dialing a phonenumber for the incoming call, wherein the phone number is stored in adatabase of the memory 4208. The memory 4208 is coupled to themicro-cellular base station controller 4204 and the switching anddatabase processor 4206. Typically, the memory 4208 has a databasestored thereon and is used for storing at least the phone number of theincoming call. Where desired, the memory 4208 may further store furtherinformation such as authentication information for the at least onemobile station or billing information for the at least one mobilestation.

Although the present invention has been described in relation toparticular preferred embodiments thereof, many variations, equivalents,modifications and other uses will become apparent to those skilled inthe art. It is preferred, therefore, that the present invention belimited not by the specific disclosure herein, but only by the appendedclaims.

XIX. Automatic Callback

Technologies that facilitate wireless communication are emerging at anever-faster rate. Such technologies are employed in end-user devicessuch as pagers, communication systems, and mail systems such as voicemail and email systems. In wireless communication systems, a need existsto provide a new service in the wireless environment for automaticallycalling back a phone number which is unavailable when the wireless userinitiates a first call. A phone may be busy when the wireless user firstcalls, and busy again when the wireless user redials the number. It isclear that the wireless user's efficiency would be increased if thewireless user may be freed from having to redial the same busy numberrepeatedly in order to complete a call.

Present wireless handsets do not provide for automatic callback to freethe user from having to redial, perhaps repeatedly, a number in order tocomplete a call. Clearly, there is a need for a system, wirelessapparatus and method for providing automatic callback for a user in awireless communication system when a called number is unavailable.

The present invention provides a system, wireless apparatus and methodthat provide an automatic callback functionality for wirelesscommunication systems. The invention enables a wireless user to choosefrom a variety of modes for completing a call when the dialed number isbusy. Rather than simply redialing the phone number an indeterminatenumber of times until the connection is made on his wireless device, thecaller may press a button or give a verbal command to initiate anautomatic callback feature.

An example is set forth below for implementing the present invention ina Wireless Centrex System (WCS). The WCS mobile station MS is notrequired to redial the same number repeatedly when he receives a busysignal. The dialing and checking procedure is performed by the WCSnetwork, thus freeing the wireless user to perform other tasks.Typically, upon the called number becoming available, the WCS systeminforms the MS using a distinctive ringing and/or tone or a ShortMessage Service (SMS) message. Where the called number is available, butthe MS already has an active call, the WCS system generates a voiceprompt or special tone on the active call to notify the MS that thecallback call is available. The MS may proceed as described below.

In one embodiment, the wireless user may activate the automatic callbackfeature by pressing a feature code, e.g., such as *66, and pressing“send” when a busy signal is received. Alternatively, after receivingthe busy signal, the user can disconnect the call and then activate thecallback feature. The WCS system sends a feature activation confirmationmessage to the MS, disconnecting the MS. A default timer is set to apredetermined time that determines the length of time that the featureis activated. Typically, the default is set to 30 minutes. The WCSsystem will automatically redial the number continuously (e.g., every 30seconds) until a connection is made and notify the MS that the call isconnected. If the predetermined default timer has expired (e.g., 30minutes), then the WCS deactivates the feature and notifies the MS thatthe feature is deactivated. There may also be other scenarios whereinthe WCS system will automatically be deactivated (e.g., when the mobilepowers down). Where the dialed number remains busy after thepredetermined time set on the default timer, the WCS system cancels thefeature and sends a message to the MS notifying the wireless user thatthe call was unable to be completed.

Where desired, the wireless user may enter a predetermined deactivationcode, e.g., *660, and push “send” to deactivate the feature.

In the example below, implementation of the present invention isaccomplished using a wireless phone in a Wireless Centrex System140(WCS). The WCS 140 provides a private wireless access system that isunconnected to any public macro-cellular system and provides Centrexservices. FIG. 1B shows a block diagram of an illustrative architectureof a WCS platform wherein the present invention may be utilized. The WCSplatform includes a local digital switch 104 (LDS), a remote digitalterminal 102 (RDT, e.g., Lucent Technologies SLC-2000), a network serverplatform 106 (NSP), voice access ports 103A, 103B (VAP) and a pluralityof associated IS-136 digital time division multiple access (TDMA)cellular or personal communications service (PCS) mobile stations 101A,101B which implement the present invention. The LDS 104 is a TR-08 andGR-303 compatible local digital switch that employs distributedintelligence, process-oriented software, and coordinated autonomouscomputing elements to provide a flexible, modular, reliable and robustdigital switching system. The LDS 104 provides a single platform foradvanced services, including Integrated Services Digital Network (ISDN),Centrex, Custom Local Area Signaling Services (CLASS), custom calling,and Advanced Intelligent Network (AIN) capabilities. The LDS 104 alsosupports X.25 packet switched data communication and circuit switcheddata, and provides a gateway to local and long distance networks. Theswitching fabric, administration, message switching, and call switchingfunctions are provided by the LDS 104.

The AIN capabilities of the LDS 104 provide AIN switch software thatenables the network provider to create, deploy, and change services tomeet user's requests. The AIN software allows the LDS 104 to act as anAIN service switching point to comrnunicate with service control pointsand intelligent peripherals. For example, the LDS 104 may be a 5ESSmanufactured by Lucent Technologies or a DMS-100 manufactured by Nortel.In the WCS configuration illustrated in FIG. 1A, the NSP 106 acts aservice control point, directing call processing on the LDS 104.

The RDT 102 is a digital loop carrier terminal that supports the plainold telephone system (POTS), ISDN, high-speed transport, and specialservices such as private lines and private branch exchange (PBX)services. For example, the RDT 102 may be implemented by a SLC2000manufactured by Lucent Technologies or an Access Node manufactured byNortel. The RDT 102 interfaces, typically at a central office, with theLDS 104. The RDT 102 provides the distribution of service interfacesbetween the LDS 104 and the user's premises, extending the digitalaccess network.

The NSP 106 provides VAP 103A, 103B control, including mobile stationand mobility management, call control, and feature applications. VAPs103A, 103B are micro-cellular base stations or radio ports that supportthe IS-136 air interface with IS-136 mobile stations such as digitalTDMA cellular/PCS (personal communications services) units 103A, 103B.The VAPs 103A, 103B support plug-and-play operations by connecting tothe RDT 102 via standard open interfaces such as the ISDN basic rateinterface (BRI) lines, typically using 2B+D signaling protocol as isknown in the art.

The IS-136 air interface standard is the EIA/TIA Interim Standard, alsoknown as the North American or U.S. TDMA standard, that addressesdigital cellular and PCS systems employing time division multiple access(TDMA). The IS-136 standard was developed to provide very flexibletechnical, service and investment options for subscribers and operators.IS-136 specifies a DCCH (Digital Control Channel) to support newfeatures controlled by a signaling and control channel between a cellsite (e.g., radio base station) and terminal equipment (e.g., mobilestation). The IS-136 air interface between the VAPs 103A, 103B and themobile stations 110 can support voice and messaging applications. Themobile stations 101A, 101B may be, but are not limited to, a terminal ora typical wireless phone having a keypad, display screen, and an alarmgenerator for generating a ringing or tone sound and translation betweentext and speech.

The automatic callback functionality of the present invention isimplemented in the above system by cellular or personal communicationsservice (PCS) mobile stations 101A, FIG. 1B also includes POTS 108 andISDN 109 interfaces for connecting analog and ISDN phones, respectively.The WCS offers a wireless access system with Centrex to provide voiceaccess and may either supplement existing wired Centrex service withwireless access or provide wireless-only stand-alone telecommunicationsservices. WCS can connect the NSP 106 to a macro-cellular network tosupport integrated mobility functions including terminal handoff andpersonal roaming features. The WCS provides location and mobilitymanagement for a WCS's subscriber mobile station 101A, 101B inside theWCS service area. Cordless communication may be provided anywhere,anytime in the WCS service area.

Though not shown in FIG. 43, the WCS system determines whether the usermay validly request the automatic callback feature functionality. Uponreceiving the origination request message, the NSP 106 analyzes thedialed digits and identifies that the automatic callback feature hasbeen requested. The NSP 106 also checks the Wireless Centrex SystemDirectory (WCSD) via the Mobile Identification Number (MIN) to determineif the MS 101 is authorized for the automatic callback featurerequested. If the validation is successful, the NSP 106 uses the MSID tolast dialed DN mapping to retrieve the DN that was dialed by the MS 101previously, sends an origination NACK with the last dialed DN message tothe VAP 103.

The VAP 103 sends an IS-136 Reorder/Intercept message to the MS 101informing the user that the automatic callback feature is activated forthe last dialed DN. If the validation is not successful or the lastdialed DN is not known, the NSP 106 sends an originating NACK messagewith reject information to the MS 101. The VAP 103 sends an IS-136Reorder/Intercept message to the MS 101 informing the user that theautomatic callback feature was not activated. FeatureActivation/Deactivation is described more fully in Section IX herein.

FIG. 43 shows a preferred embodiment for signaling flow in accordancewith the automatic callback functionality of the present invention. Asshown in (a), the NSP 106 sets the feature activation timer for apredetermined length of time (e.g., 30 minutes) when the feature isactivated. The NSP will continuously initiate calling the Last Dialed DNfor every predetermined time (e.g., 30 seconds) by sending aStartAutoCallBack message including the Mobile Station Identificationcode (MSID) and the Last Dialed Directory Number (LastDialedDN) to theVAP 103 and starts the TAC1 timer. The VAP 103 initiates the callorigination process by sending a Q.931 setup message to the LDS 104utilizing the LastDialedDN.

As described below, ISDN User Part (ISUP) call signaling is utilized inthe call pre-processing for implementing the feature of the presentinvention. ISUP defines the protocol and procedures that are used toset-up, manage, and release trunk circuits carrying data and voice callsover the public switched telephone network, PSTN. ISUP is used for ISDNand non-ISDN calls, but calls that originate and terminate at a sameswitch do not use ISUP signaling. The ISUP message format includesinformation carried in the Signaling Information Field (SIF) whichcontains a routing label, a circuit identification code, and messagetype field. The ISUP Initial Address Message is sent in a “forward”direction by each switch needed to complete the circuit between the LDSand the destination switch of the PSTN until the circuit connects to thedestination switch. The ISUP Address Complete Message is sent in the“backward” direction to indicate that the remote end of the trunkcircuit has been reserved. The originating switch then connects the MSto the trunk to complete the voice circuit. The destination switchgenerates a ringing tone. The MS user hears the ringing tone on thevoice trunk. When the called party answers, the destination switchterminates the ringing tone and sends the ISUP Answer Message to theoriginating switch. The ISUP message format depends on whether the ANSIstandard or the ITU-T standard is being implemented.

Thus, as shown in FIG. 43, portion (a), upon initiation of the automaticcallback feature, the originating switch, the LDS 104, sends an ISDNUser Part Initial Address Message (ISUP IAM) to the destination switchof the public switched telephone network (PSTN) 125 to reserve an idletrunk circuit from the originating switch to the destination switch.Then, the LDS 104 sends a Q.931 call proceeding signal to the VAP 103.The destination switch of the PSTN 125 then sends an ISDN user partAddress Complete Message (ISDN ACM) to the originating switch, the LDS104, to indicate that the remote end of the trunk circuit has beenreserved. Next, the LDS 104 sends a Q.931 alerting signal to the VAP103, and the VAP 103 sends a StartAutoCallback Proceeding message to theNSP 106 to notify the NSP 106 that an alerting message have beenreceived from the LDS 104 indicating that the dialed DN is now alertedand waiting for an answer. If the destination user is still busy whenthe call is attempted, the destination switch 125 returns an ISUP REL(release) message to LDS 104, indicating that the called user is busy.The LDS 104 initiates Q931 call clearing to the VAP. The VAP notifiesthe NSP of the failure. The NSP resets its timer and waits for apredetermined time (e.g., 30 seconds) before initiating the callbackprocedure again.

Continuing the description of FIG. 43, in portion (b), upon receivingthe StartAutoCallBack Proceeding message from the VAP 103, the NSP 106cancels timer TAC1 and sends a Page Request message (MSID, Signal) tothe VAP 103. The VAP will then send an IS-136 Page to the MS 101. The MS101 sends an IS-136 Page Response to the VAP 103. Then, the VAP 103sends the page response to the NSP 106. The NSP 106 sets timer TAC2 towait for completion of the call. The VAP 103 also sends an IS-136Digital Traffic Channel (DTC) designation to the MS 101. The MS 101 thentunes to the designated DTC. The VAP 103 sends an IS-136 Alert withinformation (Signal) to the MS 101. Note the signal can be a specialtone indicating to the MS user that the call is their automatic callbackcall. The MS 101 sends an IS-136 Mobile ACK, then an IS-136 Connectsignal, to the VAP 101. The ringback tone is initiated by the PSTN 125over the trunk to the MS 101. Then the PSTN 125 sends a ISDN User PartAnswer Message (ISUP ANM) to the originating switch, the LDS 104, whichthen sends a Q.931 connect signal to the VAP 103.

The VAP 103 then sends a Q.931 connect acknowledgement signal to the LDS104 and a signal indicating success via an origination result message(Auto Callback Result (Successful)) to the NSP 106. The NSP 106 stopstimer TAC2, and a voice path is established.

A predetermined time is set on timer TAC1 and timer TAC2 such that Q.931and IS-136 call processing may take place. If the predetermined time isexceeded, the NSP 106 will initiate procedures to clear the call. Wherethe predetermined time set on the timer TAC1 or TAC2 has expired, or theStartCallBack Result signal indicates failure, the NSP 106 sends aCancel AutoCallBack message to the VAP 103 and deactivates the automaticcallback feature for the MS 101. In addition, the NSP 106 can send ashort message to the MS 101 to indicate that the automatic callbackfeature has been cancelled or the time for the automatic callback hasexpired. Where desired, the MS 101 may re-request that the automaticcallback feature be activated either by redialing the feature code or bya voice command.

FIG. 44 is a signal flow chart showing a preferred embodiment ofsignaling flow when the MS moves from an original serving VAPo to a newVAPn before a call is connected. The MS 101 activates the AutomaticCallback feature and moves from the original VAPo 103A to another VAPn103B. The VAPn 103B sends a Handoff Result message to the NSP 106 toindicate that handoff has occurred. The NSP 106 sends CancelAutoCallBack message containing the MSID and the LastDialedDN to theVAPo 103A and starts a TACBC1 timer. If the VAPo has already initiated aQ.931 call setup process to Last Dialed DN, then the VAPo initiates aQ.931 call release procedure to clear the call attempt.

The VAPo 103A sends a Cancel AutoCallBack Ack message to the NSP 106.The NSP 106 stops the TACBC1 timer and assumes Automatic Callbackprocedures and signaling exchange with VAPn. If the NSP 106 timer TACBC1expires before receiving the Cancel AutoCallBack Result message from theVAPo or the cause for cancellation is not indicated as successful, theNSP 106 continues the new Automatic Callback feature with the VAPn 103B.

The WCS may be configured to offer service within a local accessenvironment. While the IS-136 standard is used to illustrate the bestmode for carrying out the invention, the invention is not limited to usein the IS-136 standard. The invention is also applicable to othercellular and/or PCS systems.

FIG. 45 is a flow chart showing one embodiment of steps of a method inaccordance with a preferred embodiment of the present invention. Themethod provides for, where a number called by a wireless user is busy,automatically redialing the call in a wireless communication system, andincludes the steps of: A) placing 4502 an outgoing call by a wirelessapparatus and automatically saving, where permitted, a called phonenumber for the outgoing call; and B) initiating 4504, upon one of: apredetermined button/buttons being pressed or a predetermined verbalcallback command being issued, automatic redialing of the phone numberfor the outgoing call by the wireless apparatus. Where desired, themethod may further include, upon being connected after redialing,automatically displaying 4506 the phone number for the outgoing call ona display.

Where selected, the method may further include, after placing aplurality of outgoing calls and saving the called phone numbers, wherethe called phone numbers are displayed, disposing 4508 of a firstdisplayed phone number. A displayed phone number may be disposed of byone of: moving 4510 at least a first displayed phone number to an end ofa list of phone numbers of outgoing calls or transposing 4512 the firstdisplayed phone number with a next phone number of the outgoing calls.

Where an automatic callback call is received 4514, the method mayinclude one of: pressing a button/giving a verbal command 4516 to speakimmediately with the individual returning the call; pushing abutton/giving a verbal command 4518 to place a call in progress on holdand speak immediately with the individual returning the call; andpushing a button/giving a verbal command 4520 to implement afunctionality of placing the incoming call on hold and playing aprerecorded message that explains that the call is being put on hold fora short period of time. The callback call may be terminated when thewireless user does not answer within a predetermined time.

FIG. 46 is a block diagram of a preferred embodiment of a wirelessapparatus that may be utilized for implementing the method of thepresent invention in a wireless communication system. The wirelessapparatus 4610 may include: a memory 4602, for automatically saving aphone number that was busy when called and, if selected, phone numbersof incoming calls; and a wireless automatic callback processor 4604,coupled to the memory, for initiating a wireless callback communication,upon one of: a predetermined button/buttons 4606 being pressed or apredetermined verbal callback command being issued, by automaticallyredialing the phone number for the call. The wireless apparatus may alsoinclude a display 4608, coupled to the memory 4602 and the wirelessautomatic callback processor 4604, for automatically displaying thephone number of the redialed call, and/or a phone number of an incomingcall, where permitted, on a display when the incoming call is received.Where the phone number for the incoming call is one of: unknown orsecurity-protected, the display may indicate that the phone number forthe incoming call is unable to be displayed. Alternatively, a voiceprompt or predetermined tone may indicate that the phone number for theincoming call is unable to be displayed.

Where selected, the memory may automatically save a phone number, wherepermitted, for a plurality of incoming calls and the display may providefor automatic display, where permitted, of a phone number of a mostrecent incoming call. Alternatively, the wireless automatic callbackprocessor may dispose of a first displayed phone number by moving atleast one first displayed phone number to an end of a list of phonenumbers of incoming calls received or transposing the first displayedphone number with a next phone number of the incoming calls received.The two preceding procedures may be repeated as desired.

Typically, the wireless apparatus is a wireless phone or anotherhandheld wireless communications device such as, for example, a personaldigital assistant.

A wireless communication system may include a wireless apparatusdescribed above for automatically redialing a call where a phone numberfor the call is busy when the wireless user places the call. The systemmay operate as described above or in an equivalent fashion. For example,the system may include: a switched communications network, coupled to atleast a first remote digital terminal RDT 102; at least a first networkserver platform NSP 106, coupled to at least a first local digitalswitch LDS 104; the at least first LDS 104, coupled to the at leastfirst RDT 102 and the at least first NSP 106, and, where selected, to avoice message system VMS 107; the at least first RDT 102, coupled to theat least first LDS 104, at least a first voice access port VAP 103A,103B; the at least first VAP 103A, 103B, coupled to the at least firstRDT 102 and arranged to communicate with at least a first mobile stationMS 101A, 101B; the at least first mobile station MS 101A, 101B, arrangedto communicate with the at least first VAP 103A, 103B, wherein the atleast first MS 101A, 101B includes the wireless apparatus forautomatically redialing the number, and wherein the switchedcommunications network, the at least first NSP 106, the at least firstLDS 104, the at least first RDT 102, the at least first VAP 103A, 103Band the at least first MS 101A, 101B utilize a predetermined scheme toprovide automatic callback for the wireless apparatus.

FIGS. 47A-47C represent a flow chart showing another embodiment of stepsfor implementing the automatic callback feature of the present inventionwherein the intelligence of the automatic callback feature is in the VAPrather than in the NSP as previously shown in FIG. 43. FIG. 43illustrates network centric intelligence (i.e., NSP) whereas FIGS.47A-47C illustrate a distributed intelligence embodiment. FIG. 47Aillustrates steps during call establishment/activation; FIG. 47Billustrates steps for the NSP procedure. FIG. 47C illustrates steps forthe VAP procedure. The automatic callback (ACB) feature frees the userfrom re-dialing the same busy number repeatedly. The wireless user istypically alerted by a special ringing tone when the called partybecomes available. when the NSP 106 stores 4702 a last dialed digit foran automatic callback subscriber, the NSP 106 determines 4704 whetherthe automatic callback feature can be activated by the wireless user.When the automatic callback feature cannot be activated and validated,the NSP 106 rejects 4706 the automatic callback request and informs theuser. Where the automatic callback feature can be activated andvalidated, the NSP 106 does so and starts a timer (in one embodiment thetimer is set for 30 minutes) and informs the VAP 103A, 103B to start theautomatic callback process. Then, the VAP 103A, 103B start 4710 theautomatic callback process, and the NSP 106 starts 4712 the automaticcallback process. While the VAP 103A, 103B is processing the automaticcallback procedure, the following can occur:

1. The MS moves to another VAP (either via handoff or locationregistration), and the NSP informs the former VAP to cancel theautomatic callback and the new VAP to start automatic callback.

2. The MS powers down, and power down registration is sent to the NSP.The NSP cancels the automatic callback for the VAP and for itself.

3. The MS becomes busy while the VAP is completing the call to the MSand the wireless user does not answer the call. The VAP releases thecall, cancels the automatic callback and informs the NSP. The NSPdetermines that the procedure failed because the MS is busy and informsthe VAP to restart the automatic callback procedure.

The above scenarios are valid only during the time period when the NSPhas instructed the serving VAP to initiate the automatic callbackprocedure and the VAP fails when it attempts to page the MS.

There are typically two controlling timers. Clearly, more timers may beutilized, and various times for the timers may be predetermined by theuser. In the embodiment shown, a 30 minute (T1) timer is used in the NSPand a 30 second (T2) timer is used on the VAP side. FIG. 47B illustratessteps for one embodiment implementing the NSP 4712 procedure. T1 is themaster timer. The NSP determines 4718 whether T1 has expired. When themaster timer has expired 4720, the NSP informs the VAP to cancel the ACBand cancels ACB on the NSP side. Where T1 has not expired, the NSPdetermines 4722 whether it has received a result message (msg) from theVAP. Where no result message has been received, the NSP returns tochecking whether T1 has expired 4718. Where a result message has beenreceived, the NSP determines 4724 whether the cause for receiving theresult message is a successful call. Where the automatic callback hasbeen successful, the NSP cancels the timer (T1) 4726. Where theautomatic callback has been unsuccessful, the NSP informs 4728 theserving VAP to start the automatic callback procedure.

FIG. 47C illustrates one embodiment of steps for the VAP 4710 procedure.T2 on the VAP side will only control the call establishment time for theVAP. The VAP will try every 30 seconds to establish a call with theremote user until the call is successfully connected or the procedure iscancelled. Typically, for example, the VAP may notify the NSP that theVAP plans to utilize the B channel for call establishment by sending aBchnlStatus message. The VAP will start T2 (the 30 second timer) 4732.The VAP determines 4734 whether 30 seconds has expired. If 30 secondshas not yet expired, the VAP continues to check whether the 30 secondshas expired 4734. If the 30 seconds has expired, the VAP determineswhether the NSP has notified the VAP to stop/cancel 4736 the automaticcallback procedure. If the NSP has notified the VAP to stop or cancelthe automatic callback procedure, the VAP cancels/stops 4738 theautomatic callback procedure. If the NSP has not notified the VAP tostop or cancel the automatic callback procedure, the VAP determines 4740whether there are resources available to complete the call. If resourcesare not available, the VAP returns to the step of starting T2 4732. Ifresources are available, the VAP initiates 4742 the call to thedestination user. In the diagram and similarly for FIGS. 47A and 47B, acircle 4744 simply serves to show the connection between the top portionof FIG. 47C with the bottom portion of FIG. 47C. The call setupprocedure will indicate to the VAP whether the PSTN user is still busy.If the PSTN user is still busy, the VAP releases 4748 the call, which inthis example, releases the B channel and the VAP resets the T2 timer4732. If the PSTN user is no longer busy, the VAP pages 4750 the MS.Then, the VAP determines 4752 whether the MS has responded. If the MShas not responded, the VAP releases the call, sends notification to theNSP and cancels 4764 the automatic callback procedure. If the MS hasresponded, the VAP connects 4754 the call to the MS. Then, the VAPdetermines 4756 whether the call is connected. If the call is connected,the VAP cancels 4762 the automatic callback procedure and informs theNSP. If the call is not connected, the VAP releases 4758 the call, whichin this example, releases 4760 the B channel and the VAP resets the T2timer 4732.

Thus, when the T2 timer expires, the VAP first checks whether the MS isidle and then retries to establish the call. If the remote user is busy,VAP will reset the timer. If the remote user is idle VAP will attempt toterminate the call to the MS. If the VAP fails to establish a call withthe MS (i.e., the MS is busy, powered down, moved out of coverage area)VAP will immediately cancel ACB on the VAP and inform NSP. The NSP thendetermines the status of the ACB procedure (explained in detail above).

FIG. 48 is a flow chart showing another embodiment of steps inaccordance with the method of the present invention. The method includesthe steps of: configuring 4802 a wireless communication system toautomatically redial a phone number of a call when the phone numbercalled by a wireless user is busy; and redialing 4804, automatically,the phone number when the phone number called by the wireless user isbusy.

FIG. 49 is a block diagram of one embodiment of a wireless communicationplatform for providing wireless automatic callback in accordance withthe present invention. The wireless communication platform includes atleast one mobile station 4902 and a micro-cellular base stationcontroller 4904 for wireless automatic callback that is arranged tocommunicate wirelessly with the at least one mobile station. When anumber called by the at least one mobile station 4902 is busy, themicro-cellular base station controller 4904 for wireless automaticcallback automatically redials the number to provide automatic callbackfor the at least one mobile station. The wireless communication platformmay further include a switching and database automatic callbackprocessor 4906 for wireless automatic callback that is coupled to themicro-cellular base station controller 4904 for wireless automaticcallback and a memory 4908. The switching and database automaticcallback processor 4906 provides processing for wireless automaticcallback for the at least one mobile station upon one of: apredetermined button/buttons being pressed or a predetermined verbalcallback command being issued, by automatically redialing the number.The memory 4908 is coupled to the micro-cellular base station controller4904 for wireless automatic callback and to the switching and databaseautomatic callback processor 4906. The memory 4908 has a database forstoring at least the number redialed. Where selected, the memory 4908may further store information for authentication and/or billinginformation for the at least one mobile station.

Although the present invention has been described in relation toparticular preferred embodiments thereof, many variations, equivalents,modifications and other uses will become apparent to those skilled inthe art. It is preferred, therefore, that the present invention belimited not by the specific disclosure herein, but only by the appendedclaims.

XX. Speed Calling

The speed calling feature allows a subscriber to compile a list of phonenumbers in which each phone number is associated with a unique speedcalling code. A subscriber can provision a unique speed calling code forone or more telephone numbers. When an MS user enters a valid speedcalling code, the WCS system will complete the call using the telephonenumber in the speed calling list corresponding to the speed calling codeentered.

There are several ways a subscriber can provision a telephone number forspeed calling. For example, the user may access the Internet or aweb-based interface such as a WCS web site and input and update a listof phone numbers having speed calling. Also, the subscriber may contacta customer care center representative by phone and verbally communicatethe numbers through any type of communications unit (e.g., cell phone,landline phone, wireless palm top computer phone, etc.). Alternatively,a user may be directed through an automated phone menu to input thenumbers by use of a communications unit keypad or voice recognitionsystem.

According to one embodiment, the user may provision the speed callingtelephone numbers through the WCS system. In this regard, the subscribermay activate the feature by entering a feature activation code, a speedcalling code (e.g., 1-30) followed by a phone number (e.g.,*75*1#5555151) into the keypad of MS 101A and then pressing the “send”button. Actuation of the “send” button sends the feature activationmessage to the WCS system (e.g., NSP 106). The WCS system then mayacknowledge activation of the feature, by returning a short message tothe MS 101A, or alternatively an aural communication, including identityof the feature activated, the speed calling code and phone number, forexample. In addition, a message indication that a call originationrequest has been rejected can be used to provide featureactivation/deactivation status information.

In a further modification, the speed calling code may be automaticallyassigned such as with the first available speed calling code. Thus, thesubscriber might send the feature activation code followed by thetelephone number (e.g., *75*#5555151) to the WCS system. In thisinstance, when the subscriber fails to enter a speed calling code, aspeed calling code may be automatically assigned to the telephonenumber. Illustratively, if thirty codes are available (code numbers1-30) and code numbers 1, 2, 4 and 7 have been assigned, the system canassign the next available code, which would be code number 3 to thetelephone number input by the subscriber. If all available speed callingcodes are assigned, the system can send a short message or aural messageindicating the same, or can send status information with a messageindicating that a call origination request has been rejected. Also, thesubscriber may enter a code requesting the system to identify thetelephone number associated with a speed calling code.

To delete a phone number from the speed call list, the subscriber mayoverwrite the existing phone number assigned to a speed call code withanother number. Alternatively, the subscriber may enter a featuredeactivation code followed by the telephone number and press the “send”button. Also, the subscriber may deactivate the speed calling codes forall numbers by entering a global feature deactivation code and the“send” button on the MS 101A. A more detailed discussion of featureactivation and deactivation is provided at other places in the instantdescription, for example at section IX, above.

To implement the speed call feature, the subscriber dials the speedcalling code (e.g., *1) for the desired telephone number and presses the“send” button on MS 101A. If the speed call code entered is unassigned,an error message will be returned to the subscriber by a short messageor otherwise.

According to an illustrative embodiment of the invention, the speed calllist may be stored in a memory in the NSP 106 or a memory locationaccessible to the NSP 106. The list may include any amount of numbersdepending on the capacity of the memory employed. In one embodiment, upto thirty numbers may be defined to have a unique speed call code andthe size of the telephone numbers can range from 1-17 digits.

FIG. 50 provides an exemplary call flow diagram for implementing thespeed call feature according to an illustrative embodiment of thepresent invention. While the IS-136 standard is used to illustrate oneimplementation of the present invention, it should be understood thatthe present invention is applicable to other cellular or PCS systems.

When a WCS subscriber wants to place a call utilizing speed calling, thesubscriber inputs the speed calling code *n, where n is the code andactuates the “send” button. In response, MS 101A sends an IS-136origination [DN=*n] message 5002 to a VAP 103A at which the MS 101A isregistered. Also, the MS 101A sends an IS-136 serial number message 5004to the VAP 103A. In response, the VAP 103A sends a proprietaryorigination request message (Origination Request [dialed digit=*N]) 5006to the NSP 106 and starts timer T01. The NSP 106 receives theorigination request message 5006 and identifies that a speed callattempt is being made.

The NSP 106 then determines whether MS 101A subscribes to the speed callfeature by comparing the MIN of MS 101A with an authorized subscriberlist maintained in the WCSD. If the MS 101A is not authorized for thespeed call feature, then the NSP 106 sends the VAP 103A an originationnon-acknowledgment (NACK) message (not shown) and indicates that the MS101A does not subscribe to the speed call feature. The timer T01 iscanceled and the VAP 103A then notifies the MS 101A subscriber through ashort message or aural message that it does not subscribe to the speedcall feature.

If the MS 101A is authorized for the speed call feature, then the NSP106 determines whether the speed call code input by the subscribercorresponds to a telephone number. If no number corresponds to theentered speed call code, a NACK message is sent to the VAP 103Aincluding a DN unavailable message and the timer T01 is canceled. The DNunavailable message is then delivered by the VAP 103A to the MS 101A.

If the MS 101A is authorized fro the speed call feature and a phonenumber corresponds to the speed call code entered, the NSP retrieves thetelephone number associated with the speed dialing code from the speeddial list. Then, the NSP 106 sends an origination acknowledgementmessage 5008 (origination ACK (SpeedDial DN)) including the telephonenumber to the VAP 103A and starts the timer TSC1. Responsive to theorigination acknowledgement message 5008, the VAP 103A cancels timer T01and initiates a Q.931 call set up procedure using the telephone numbercorresponding to the speed dial code, i.e., speed dial DN. If the T01timer expires before the VAP 103A receives the originationacknowledgement message 5008, the VAP 103A sends an IS-136reorder/intercept message (not shown) to MS 101A including informationabout what went wrong similar to when the VAP 103A receives anorigination NACK message.

The call set up procedure is similar to call set up procedure describedelsewhere in this application, but will be described here forcompleteness. To set up the call, the VAP 103A reserves an RF DTCchannel and sends a Q.931 setup [speed dial DN] message 5010 to the LDS104. The LDS 104 then examines the speed dial DN in the Q.931 setupmessage 5010 and sends an ISUP IAM message 5012 to a far end switch inthe PSTN 125 for end-to-end connectivity. Also, the LDS 104 sends aQ.931 call proceeding message 5014 to the VAP 103A. The VAP 103A thensends an IS-136 Digital Traffic Channel (DTC) Designation 5016 messageto the MS 101A so that MS 101A may tune to the designated trafficchannel. MS 101A informs VAP 103A that it is using the designated DTC byresponding with an MS on DTC message 5018. The VAP 103A then detectsthat the MS 101A is tuned to designated traffic channel, and cutsthrough the voice path 5034 between the RF DTC channel and an ISDN Bchannel.

The destination switch in the PSTN 125 sends an ISUP ACM message 5020 tothe LDS 104. In response, the LDS 104 sends a Q.931 alerting message5022 to VAP 103A. Next, a ringback tone 5024 is delivered to the MS 101Afrom the destination switch. Also, the PSTN 125 sends an ISUP ANMmessage 5026 to the LDS 104. Following receipt of the ISUP ANM message5026, the LDS 104 sends a Q.931 connect message 5028 to the VAP 103A,removes the ringback tone 5024, and cuts through the voice path 5034.The VAP 103A then sends a Q.931 connect ACK message 5030 back to the LDS104 to acknowledge the connection. Responsive to the Q.931 connect ACKmessage 5030, the VAP 103A sends origination result [success] message5032 to the NSP 106 for billing and other OAM&P purposes. At this point,voice path 5034 has been established and the call proceeds between theMS 101A and the party called using the speed call code.

While the above description relates to an example of speed calling for aparty coupled to a PSTN, it should be understood that a speed callingcode may be set up for any party which a subscriber may call including,but not limited to, a WCS subscriber, a landline subscriber, and acellular subscriber. Also, multiple phone numbers can be assigned to asingle unique speed calling code such that entry of the speed callingcode will initiate a call involving parties at each of the multiplephone numbers in a conference call. Reference is made herein to thedescription of conference calling in Section XXI below, which can bemodified to provide for a speed call code to originate a three-way call,for example.

XXI. Conference Calling

A. Adding A Party To An Existing Call

The conference call feature/function allows a MS 101 user to talk withtwo or more parties at the same time. Once the MS 101 user is on a firstactive call, he can enter a feature code, for example by keying in *33#on the MS 101 keypad followed by a third party's DN (conference with DN)and then pressing a transmit key, for example, the “send” button, toinitiate a conference call. Once validated by the WCS networkdetermining that the MS-101 user is authorized to use the conferencecalling feature/function, an announcement is provided, for example, avoice prompt or a special tone will be heard by the MS 101 user (andoptionally to the second party to an active call) indicating that aconference call connection (e.g., Three-Way Calling) has been requested.After the third party answers, the MS 101 user may then enter anothercode, for example by pressing the “send” button on the MS 101, to beginthe multi-party conference call conversation.

The following detailed description of the conference callfeature/function is described in terms of a three way call for ease ofexplanation and because one typical local digital switch has three wayswitches for each wireline. However, one skilled in the art willrecognize that a switch having greater than three possible lineconnections (i.e., more than a three-way switch) may be provided in thelocal digital switch, e.g., a six way switch. Therefore, the conferencecall feature/function, although described in specific embodiments belowillustrating three-way calling, is also applicable to conference callshaving more than three parties by repeating portions of the conferencecall initiation and setup procedures.

Further, the signal flows used for Three-Way calls in this document aredirected to comply with the Lucent 5ESS local digital switches and mayapply to other local digital switches, such is the Nortel DMS-100 localdigital switches, with or without modifications. Since the interfacebetween LDS 104 and the VAP 103 is based on standard Q.931 messages itis supported by all LDSs. So, with minimum changes (if needed), theexemplary call flow described with reference to the Lucent 5ESS wouldwork with other LDSs such as the Nortel DMS-100.

The conference call feature/function provides an MS 101 user with aconvenient and user friendly method of creating a multi-party call. Oncethe MS 101 user has established an active call, for example a two-waycall, with one or more other parties the MS 101 user is free to initiateadding a person for a conference call. First, while on an active call,the MS 101 user may indicate to the other party that a Three-Way callwill be requested. After entering the conference call feature code,e.g., pressing the *33#, followed by the third party's DN, the MS 101user will transmit this information to the WCS by, for example, pressingthe “send” button. The existing second party is then put on hold and theMS 101 user initiating the conference call feature/function will beprovided an announcement, for example, a voice prompt or a special toneon the MS 101 indicating the Three-Way call activation is nowproceeding. The voice prompt or special tone may also be provided to theother party, or alternatively other audible sounds may be provided tothe other party such as music.

If the MS 101 user initiates the conference call feature/function duringan already active three-way call they initiated, and the LDS 104 isequipped with a switch that is capable of handling connection of anotherparty (i.e., more than a three-way switch), the request for anotherconference call initiation will be honored and a similar connectionprocedure will ensue. However, if the LDS 104 is equipped with only athree-way switch, the request for another conference call initiation toadd an additional party will be rejected and an appropriate notification(e.g., an announcement) of the limitation to a three-way call will beprovided to the MS 101 user. Furthermore, if the MS 101 user transmitsan empty message by, for example, pressing the “send” button before theoriginal call is put on hold, the NSP 106 will ignore it.

When the call goes through to the third party, the MS 101 user whoinitiated the conference call will hear the ringing tone. If the thirdparty answers, the MS 101 user can press a key on the MS 101, forexample, the “send” button, (within a certain time period) to retrievethe held call(s) and complete the conference call (e.g., Three-Way)connection. In one alternative embodiment, the MS 101 cannot disconnecta third party who answers without first establishing a three-wayconnection. If the third party answers and the initiator presses atransmit key, for example, the “send” button once, to set up a three-waycall but the original two-way call could not be retrieved for somereason (e.g., the party to the original two-way call on hold has hungup), the two-way call with the second called party will continue. Anindicator, for example a voice prompt, indicating that the party on holdcan not be connected may be provided to the MS 101 user who initiatedthe conference call feature/function.

If the third party answers and disconnects before the MS 101 user canestablish a conference call (e.g., a three-way call), the MS 101 usercan again transmit a message, by for example pressing a the “send”button once, and retrieve the original call. Further, if the connectionto third party fails as a result of the switch being unable to connectto the third party (rather than the third party is busy or is notanswering the phone), the MS 101 user can enter a code message, forexample, press the “send” button once, to retrieve the original callplaced on hold. On the other hand, if the third party's line is busy orthe third party does not answer the phone, the MS 101 can enter anothercode message, for example the MS 101 can press the “send” button twice,to disconnect the second leg of the call and retrieve the original callon hold. Once again, if the original called party has alreadydisconnected, an indication that the original called party isdisconnected may be provided, e.g., an announcement such as a voiceprompt may be played to the MS 101 user.

Furthermore, if the third party's voice mail answers, the three-way callis assumed to be complete. The MS 101 user may enter a code message, forexample they can press the “send” button once, within a certain amountof time and establish a three-way conference. In one alternativeembodiment the initiator can disconnect from the third party voice mailand end the conference call by pressing the “send” button twice onlyafter the three-way call has been established. Thus, in this embodimentthe MS 101 conference call initiator must establish the conference callconnection by retrieving the original call in order to disconnect fromthe third party's voice mail.

At any time during an established conference call, the MS 101 user canenter a feature code message, for example by pressing the “send” buttontwice quickly (within a certain amount of time, e.g., within a fewseconds) and disconnect the last added call. To end all calls the MS 101user can enter another code, for example the initiator may just pressthe “End” button.

Referring now to FIGS. 51 and 52, a discussion of various scenarios fora preferred embodiment having a three-way conference call is illustratedusing a process flow chart. In a first instance, an MS 101 user callsanother party, either another MS 101 user or a PSTN user, andestablishes an active two-way call in progress at step 5101. During theactive two-way call the MS 101 initiates a three-way conference call byentering a feature code and a conference to directory number (DN) of theparty to be added (e.g., third party), and then press a processinitiation key by pressing, for example, the “send” key on the MS 101 asshown in step 5102. In the next step, feature validation decision step5103, the NSP 106 determines whether the MS 101 user is authorized touse the conference call feature/function (i.e., the MS 101 usersubscribes for the feature), and if so, notifies the VAP 103 to goforward with the conference call set up. However, if the MS 101 user isnot authorized to use the conference call feature/function, the NSP 106will return the MS 101 user to the two-way call in progress state atstep 5101. Upon returning to step 5101 an announcement may be played toMS 101 user indicating that the conference call feature/function is notavailable and information on how to subscribe for the service.

After the VAP 103 is instructed by the NSP 106 to proceed with theconference call setup, the VAP 103 initiates, for example, a three-waycall by first instituting a second call reference (CR=2) at step 5104and places the first call, first call reference (CR=1), on hold. Next,at decision step 5105, the VAP 103 determines if the third party isbeing alerted. If so, the VAP 103 then waits to see if the third partyanswers. If not, VAP 103 disconnects/releases call reference 2 in step5209 (See FIG. 52) and awaits the MS 101 user input, by pressing forexample the “send” key, to determine if the original call is retrieved(steps 5203 and 5205) or if the original call is also dropped (step5204). If the MS 101 user presses the process initiation key againbetween initiating the three-way call at step 5104 and providing thethird party an alert at step 5105, the input is ignored.

At decision step 5106 the VAP 103 determines if the third party has beenconnected to the MS 101 user and has answered. If so, the MS 101 and thethird party are connected by the LDS 104 with a voice path for thesecond call reference (CR=2) at step 5107. If not, the VAP 103disconnects/releases the third party (CR=2) at step 5209 and awaits MS101 user input by, for example the MS 101 user pressing the “send”button, to attempt to retrieve the second party from hold tore-establish the original two-way call at step 5205 (See FIG. 52) orrelease all resources at step 5204. If possible, the VAP 103 reconnectsthe MS 101 user with the second party that was placed on hold and thusre-establishes the two-way call in progress at step 5205. If the VAP cannot retrieve the second party it releases all resources at step 5204.

If the MS 101 user presses the conference call initiation key, forexample the “send” key, twice between steps 5105 and 5106 before thethird party answers, the VAP 104 will disconnect the third party,attempt to retrieve the second party, and re-establish a two-way call inprogress, as indicated at steps 5201-5205. However, if the MS 101 userpresses the conference call initiation key, for example the “send” key,once between step 5105 and 5106 the input will be ignored.

Once the MS 101 user is connected in a two-way voice path with the thirdparty the MS 101 user may enter a code message, by pressing at any time,for example the “send” button to enter the process initiate button, asindicated at step 5108. This will retrieve the second party and connectthem to the existing voice path between the MS 101 and the third partyso that a three-way call is in progress as indicated at steps 5109 and5110. If the MS 101 user does not enter a code message by, for example,pressing the “send” button or the second party can not be retrieved, theLDS 104 will leave the MS 101 user connected with the third party atstep 5107. Further, if the MS 101 user enters a code message bypressing, for example, the “send” button again before the three-way callis established, the input will be ignored. On the other hand, if the MS101 user enters a different code message by, for example, pressing theconference call initiation key, e.g., the “send” key twice after thethree-way call has been established, as indicated at step 5206, the NSP106 will instruct the VAP 103 to drop the third party as indicated instep 5207. Next, the VAP 103 will retain the MS 101 user and the secondparty in a two-way call as indicated in step 5208. If the MS 101 userenters a code message by pressing, e.g., the conference call initiationkey, for example the “send” key, only once after the three-way call hasbeen established, it will be ignored.

An embodiment of the conference call feature/function of the presentinvention illustrating an exemplary three-way call signal flow is shownin FIG. 53. A successful conference call setup procedure has in generalfour basic steps. These general steps are: (1) establishing a firstactive call between an MS 101 user and a second party (or parties); (2)placing the active call between the MS 101 user and the second party (orparties) on hold; (3) establishing a second active call between the MS101 user and a party to be added, e.g., a third party; and (4)re-connecting the second party on hold to the second active call. Adetailed discussion of the signal flow for achieving each of these stepsand more specific steps of a successful conference call process followsfor an exemplary embodiment using a three party conference call as anexample.

First, the MS 101 user is a party to an active call with a party havinga PSTN DN1 125 a indicated as Call in progress (CR=1) 5301. When the MS101 user wants to set up a three-way conference call with another PSTNuser, PSTN DN2 125 b (whose DN is herein referred to as ThreeWayDN), theMS 101 user enters the conference call feature code, for example “*33#”and the party to be added DN digits in the format of *33#ThreeWayDN andpresses, for example, the “send” button on MS 101. The MS 101 sends toVAP 103 an IS-136 Send Burst DTMF message for each digit pressed. In theconference call procedure, the VAP 103 is responsible for receiving andbuffering the digits, i.e. *33#ThreeWayDN, generated by the MS 101 inthe form of IS-136 Send Burst DTMF messages. By pressing the “send”button, the MS 101 generates an IS-136 Flash With Info message whichinitiates packing of the previously depressed digits, so that the VAP103 construes as one message the string of digits sequentially inputearlier, i.e., the IS-136 Send Burst DTMF [*33#ThreeWayDN] 5302 message.Upon receiving each IS-136 Send Burst DTMF message from the MS 101, theVAP 103 sends an IS-136 Send Burst DTMF ACK 5303 message to the MS 101.

The IS-136 Send Burst DTMF 5302 messages include data fields such as:Protocol Discriminator, Message Type, Request number (DN), and Digit.The IS-136 Send Burst DTMF ACK 5303 message includes data fields such asProtocol Discriminator, Message Type, Request number (DN), RemainingLength, and Last Decoded Parameter.

The MS 101 user initiates a conference call feature/function by enteringa command, for example, by pressing the “send” key on the MS 101, whichresults in a IS-136 Flash with Info 5304 message being sent from the MS101 to the VAP 103. After receiving the Flash With Info 5304 message,the VAP 103 acknowledges receipt by sending Flash With Info Ack 5306message to the MS 101 and requests initiation of a conference callfeature/function setup procedure by sending a novel Feature Request[*33#ThreeWayDN] 5305 message including the buffered digits*33#ThreeWayDN, to the NSP 106.

Upon receiving the Feature Request message from the VAP 103, the NSP 106searches the WCSD in, for example memory 1240, and verifies that the MS101 user has subscribed to the conference call feature, that thethree-way call feature (assuming an LDS 104 has a three-way switch), andthat the MS 101 user is not active on another three-way call initiatedby him. The NSP 106 then sends a unique Feature Request ACK message,Feature Request ACK [3-Way, ThreeWayDN] 5307 message, containing the3-Way as the action and the ThreeWayDN as the CalledDN. It also startsthe T31 timer that will wait for the 3-Way Proceeding [success] 5324message. In the situation where the MS 101 is authorized for theconference call capability and the LDS 104 has sufficient switchcapacity to add another party to the conference call, the VAP 103 willplay an announcement (or tone) to the MS 101 informing the MS 101 user(and optionally all parties to the conference call) that the conferencecall setup has been initiated, for example, Voice Prompt (3-way callinitiated) 5308. On the other hand, if the MS 101 user who initiates theconference call is not authorized to make a three-way call, the NSP 106sends a Feature Request ACK message with the action as Invalid 3-Way, soas to trigger an indication to the MS 101 user that the conference callfeature/function is not available to them and the normal 2-way call willremain in progress. In either case, the VAP 103 may play the appropriatetaped or voice synthesis generated announcement using, for example, theVPU 1235, or alternatively generates a tone to the MS 101 user andoptionally to the PSTN DN1 125 a or the MS 101 may display a textmessage, as the indication of status.

Then the VAP 103 sends a Q.931 Info [CR=1,FA=Conf] 5309 message with theFeature Activation set to conference call to the LDS 104 to initiate athree-way conference call, updates a record to identify that this is athree-way call, and starts the T32 timer awaiting a response from theLDS 104. The LDS 104 acknowledges by sending a Q.931 Info [CR=1,FI=Conf,Active] 5310 message with the Feature Indication set to anactive conference call and the VAP 103 cancels the T32 time.

At this point, the WCS begins a procedure to place the first callbetween the MS 101 user and the 2nd party at PSTN DN1 125 a on hold toallow connection between the MS 101 user and a 3rd party on anotherline. Once the VAP 104 gets a Q.931 Info message from the LDS 104 itcancels the T32 timer, sends a Q.932 Hold [CR=1] 5311 message to the LDS104 instructing the LDS 104 to place the existing call with PSTN DN1 125a on hold, and starts a THh timer. However, if the T32 expires, the VAP103 will log an error and send a 3-Way Proceeding message as fail to theNSP 106 with the cause value indicating that 3-way call could not beinitiated. The NSP 106 and VAP 103 will update the call recordinformation to indicate that the normal 2-way call is now in progress.

If the T32 time does not expire, the LDS 104 puts the first leg of thecall on hold, i.e., proceeds to place the voice path with PSTN DN1 125 aon hold, and sends a Q.931 Hold Ack [CR=1] 5312 message to the VAP 103indicating that the first active call has been placed on hold. The VAP103 cancels timer THh and sends a Q.931 Setup [CR=2, ThreeWayDN] 5313message to the LDS 104, including the second call reference number(CR=2) and the ThreeWayDN, to setup the conference call to the thirdparty [CR=2] on the same B-channel. However, if the timer THh expires,the VAP 103 will log an error and send a 3-Way Proceeding 5316 messageas fail to the NSP 106 with the cause value indicating that 3-way callcould not be held. The VAP 103 and NSP 106 will update the call recordinformation to indicate that the normal 2-way call is now in progress.

If timer THh does not expire, the VAP 103 updates the information aboutthis call in the appropriate record to identify that a 3-Way call isbeing established and starts the T303 timer awaiting a Q.931 CallProceeding 5316 message from the LDS 104. Thus, the first referencedcall (CR=1) is now held by the LDS 104 awaiting the connection of MS 101with other parties (Call Held by LDS (CR=1) 5315. The NSP 106 updatesthe information about this call in the appropriate record in the WCSDof, for example, in the memory 1240.

When the first call between the MS 101 user and the second party, PSTNDN1 125 a has been put on hold the WCS then continues with theconference call setup procedure by performing a call setup between theMS 101 and a party to be added to the conference call, for example, athird party at PSTN DN2 125 b. First, the LDS 104 processes the Q.931Setup [CR=2, ThreeWayDN] 5313 message and sends a Q.931 Call Proceeding5316 message to the VAP 103 indicating to the VAP 103 that the call toPSTN DN1 125 b is being initiated. Once the VAP 103 receives a Q.931Call Proceeding 5316 message from the LDS 104, it cancels the T303 timerand starts T310 timer waiting for Q.931 Alerting 5319 message from theLDS 104. The VAP 103 does not have to do anything on the RF side becausethe MS 101 is already on the DTC. However, if the timer T303 expires,the VAP 103 will send a novel 3-Way Proceeding 5324 message as “fail” tothe NSP 106 with a proper cause value. It will also send a Q.931 ReleaseComplete [CR=2] 5330 message to the LDS 104. After this the VAP 103 willstart a timer T34 waiting for a Flash with Info message from the MS 101(this would indicate that the mobile wants to retrieve the originalcall).

Next, the LDS 104 sends an initial address message, ISUP IAM 5317, tothe ThreeWayDN, in this example another PSTN LDS, PSTN DN2 125 b. Inresponse, the PSTN DN2 125 b sends an address complete message, ISUP ACM5318, to indicate that a communication link has been made with PSTN DN2125 b. Next, the LDS 104 sends a Q.931 Alerting 5319 message to the VAP103 so that the VAP 103 and LDS 104 can provide MS 101 Ringback Tone5320 indicating that PSTN DN2 125 b is being alerted of an incomingcall. When the VAP 103 receives a Q.931 Alerting 5319 message from theLDS 104, it cancels the timer T310 and starts T301 timer waiting forQ.931 Connect 5322 message from the LDS 104. However, if the timer T310expires, the VAP 103 will follow disconnect procedure by sending Q.931Disconnect (CR=2) message to the LDS 104. The LDS 104 will respond withRelease (CR=2) 5329 message. The VAP 103 will continue to follow thesame procedure as above; the VAP 103 will also send a Q.931 ReleaseComplete [CR=2] 5330 message to the LDS 104. After this the VAP 103 willstart a timer T34 waiting for a Flash with Info message from the MS 101(this would indicate that the mobile wants to retrieve the originalcall).

When the third party at PSTN DN2 125 b answers the call an answermessage, ISUP ANM 5321, is sent from PSTN DN2 125 b to LDS 104. Inresponse, the LDS 104 sends a Q.931 Connect 5322 message to the VAP 103.When the VAP 103 gets the Q.931 Connect 5322 message from the LDS 104,it recognizes that this message corresponds to a three-way call andcancels the T301 timer. If the timer T310 expires, the VAP 103 willfollow disconnect procedure by sending Q.931 Disconnect (CR=2) messageto the LDS 104. The LDS 104 will respond with Release (CR=2) 5329message. The VAP 103 will continue to follow the same procedure asabove; the VAP 103 will also send a Q.931 Release Complete [CR=2] 5330message to the LDS 104. After this the VAP 103 will start a timer T34waiting for a Flash with Info message from the MS 101. Otherwise, theVAP 103 then sends a Q.931 Connect ACK 5323 message to the LDS 104acknowledging the second call connection has been made between the MS101 and PSTN DN2 125 b and starts a T34 timer. (The voice path of thesecond call is illustrated in FIG. 53 as dashed arrow lines labeled Callin progress (CR=2) 5414 from the PSTN DN2 125 b to MS 101.)

Once the voice path has been established the VAP 103 sends a novel 3-WayProceeding [success] 5324 message to the NSP 106 indicating that thethird party has been successfully added to the conference call bycompleting the second call between MS 101 and PSTN DN2 125 b. Thismessage includes the MSID, the Call Reference Number (CR=2), and theCause (Success/Fail) fields. (The cause field in the 3-Way Proceedingmessage may contain the comments, for example: 3rd party answered(success), 3-way call hold fail, 3-way call initiate fail, or 3rd partydid not answer.) At this point, establishing a second call between theparty to be added, in this case a third party, has been completed andthus the MS 101 for the conference call setup procedure is complete withthe exception of a few administrative details to be performed by the NSP106.

When the NSP 106 gets a 3-Way Proceeding [success] 5324 message itupdates the information about this call in the appropriate record in theWCSD to, among other things, capture the call usage time for the new legof the call. The NSP 106 cancels the T31 timer, updates the call recordinformation and starts the T36 timer that waits for the 3-way Result[success] 5433 message from the VAP 103 indicating that the conferencecall setup has been completed successfully. However, if the second callto the third party is not connected for whatever reason, for example,the T31 timer expires and/or the NSP 106 receives 3rd Party Answeredmessage as a “fail”, the NSP 106 will send a 3-Way Disconnect message tothe VAP 103 to disconnect the attempted connection with the third party,retrieve the original call with PSTN DN1 which was placed on hold (asdiscussed in more detail below), and update the call information recordto indicate that a normal 2-way call is now in progress.

If the MS 101 user had requested to set up a conference call by addinganother MS 101 rather than the PSTN DN2 125 b, the call setup procedurewould have followed the sequence described in other areas of theinvention for call setup from one MS 101 to another MS 101 in the WCS.

Next, the conference call setup procedure connects the original callwith the second party at PSTN DN1 125 a on hold with the active callbetween MS 101 and the third party at PSTN DN2 125 b. If the MS 101 useronce again inputs the initiation code, for example by pressing the“send” button once, an IS-136 Flash with Info 5325 message is sent tothe VAP 103 requesting that the second party on hold be added to thetwo-way call between the MS 101 user and the third party. The VAP 103cancels the T34 timer, sends a Q.932 Retrieve [CR=1] 5326 message to theLDS 104 indicating that the MS 101 user has requested that the call onhold be retrieve so that it and the active call be combined to form, inthis case, a three way conference call, starts the TRr timer, and sendsan IS-136 Flash with Info Ack 5327 message to the MS 101. However, ifthe timer T34 expires, the VAP 103 will follow the Release procedure torelease CR=1 and send 3-Way Result as fail to the NSP 106. A 2-Way callwith third party would continue.

When the LDS 104 receives the Q.932 Retrieve [CR=1] 5326 message fromthe VAP 103 (after the third party has answered), it verifies that theoriginal called party, in this case the second party, is still presenton hold, and sends a Retrieve Ack 5328 message to the VAP 103 indicatingthat the original call on hold has been retrieved. The LDS 104 thenmergers the calls, CR=2 with CR=1. When the VAP 103 receives Q.932Retrieve Ack [CR=1] message from the LDS 106, it will stop the TRr timerand start T35 timer. However, if the timer TRr expires as a result ofthe VAP 103 not receiving the Q.932 Retrieve Ack 5327 message because,for example, the second party hangs up or is some way disconnected, theVAP 103 will log an error and send a 3-way Result message as fail to theNSP 106 and the 2-way call [CR=2] with the third party will continue. Inthe case of such a failure to retrieve the first call placed on hold,the VAP 103 may also play a voice prompt to the MS 101 user indicatingthat the 3-way call could not be completed.

After merging the two legs of the call, CR=1 and CR=2, the LDS 104 sendsa Q.931 Release [CR=2] 5329 message to the VAP 103 to release the secondcall reference (CR=2) while retaining the three (or more) parties on theconference call. Then VAP 103 cancels timer T35 and releases (clears)the second call reference CR=2 and sends a Q.931 Release Complete [CR=2]5330 to the LDS 104. However, if the timer T35 expires, the VAP 103 willlog an error. The 3-way call is in progress so the VAP 103 will send aQ.931 Release [CR=2] 5329 message to the LDS 104 to release the secondcall reference. Once the VAP 103 gets a Q.931 Release Complete [CR=2]5330 message from the LDS, it will send a 3-way Result [success] 5331message to the NSP 106.

In any case, the VAP 103 sends a novel 3-Way Result [success] 5331message to the NSP 106 indicating that the release of CR=2 issuccessful. The 3-Way Result message includes MSID, Call ReferenceNumber, and Cause fields. Then the NSP 106 cancels the timer T36 andupdates the call record information to indicate successful setup of aconference call, in this case a three-way call, and that the conferencecall is now in progress (indicated as the dashed arrows labeled (3-WayCall In-Progress (CR=1) 5332).

However, if the NSP 106 receives a 3-Way Result message from the VAP 103indicating a “fail”, the NSP 106 will cancel the T36 timer and updatethe call record information to indicate that the normal 2-way call[CR=2] is in progress. If the T36 timer expires, the NSP 106 willinitiate a Release procedure on CR=2. In either case, the NSP 106 maysend a Play Voice Prompt message to the VAP 103 to inform the user thatthe conference call could not be completed and a two-way call willcontinue. Further, if any party disconnects during the establishment ofa three-way call, the NSP 106 will get a WCS specific Release message.Then the NSP 106 will update its call record information and resourcetable accordingly.

In some circumstances, although the third party may answer, theequipment may fail to be able to connect the third party to the originalcall. In such a case, the WCS will need to notify the MS 101 user andthe MS 101 user may wish to retrieve the original call. FIG. 54 belowgives the signal flow for one exemplary embodiment when the third partycould not be connected.

The signal flow in the case where the third party could not be connectedto the conference call is essentially the same as described for FIG. 53up to the point where the VAP 103 sends 3-Way Proceeding [success] 5324message. In general, the original call, call reference 1, is placed onhold by the LDS, Call Held by LDS(CR=1) 5315 message. Subsequently, thethird party line PSTN DN2 125 b sends an ISUP ACM 5318 message to theLDS 104. In response the LDS provides a Q.931 Alerting 5319 message tothe VAP 103 and a Ringback Tone 5320 to the MS 101. However, in the casewhere the third party could not be connected to the conference call, the3-Way Proceeding message from the VAP 103 results in a “fail” messagebeing sent to the NSP 106, i.e., 3-Way Proceeding [fail] 5452.

After sending 3-Way Proceeding [fail] 5452 message, the VAP will start atimer T34 waiting for Flash with Info message from the mobile andprovide an indication to the MS 101 user that the third party can not beconnected. For example, the MS 101 use may receive a Voice Prompt: Cannot connect 3rd Party 5453 or a similar text message, which prompts theMS 101 user to respond accordingly. If the MS 101 user enters theinitiation code, for example, by pressing the “send” key, the VAP 103will be sent a IS-136 Flash with Info 5454 message from the MS 101. TheVAP 103 will cancel timer T34, send a Q.931 Retrieve [CR=1] 5455 messageto the LDS 104 to re-connect with the original call, send and IS-136Flash with Info Ack [CR=1] 5456 message to the MS 101, and start timerTRr. However, if the timer T34 expires, the VAP 103 will follow adisconnect procedure and send a WCS Release message to the NSP 106 sothat all calls are disconnected and all resources released. If the timeT34 does not expire, the LDS responds with Q.931 Retrieve ACK [CR=1]5457 message and the VAP 103 will cancel the TRr timer and update itscall record to reflect that the original call has been received and theconference call latest attempt to add a party has been cancelled. TheWCS will establish the original call, for example, 2-Way Call inProgress(CR=1) 5458. On the other hand, if the timer TRr expires, theVAP 103 will release RF resources, clear the call reference on its side,send a Q.931 Release [CR=1] message to the LDS 104. Once the VAP 103receives Q.931 Release Complete message from the LDS 104, it will send aWCS Release message to the NSP 106 with a proper cause value.

In some instances the MS 101 user may wish to retrieve the original callwith the 2nd party before a conference call, e.g., a three way call, isestablished. FIG. 55 depicts the signal flow for the scenario when theMS 101 user wants to retrieve the original call with the second partybefore the third party answers. To do so, the MS 101 user can enter thefeature initiation code twice, for example, he may press the “send”button twice in certain scenarios. In particular, if the original callwith the second party is on hold and the third party has not yetanswered the incoming call, the conference call setup procedure can beeasily cancelled by, for example, the MS 101 user entering the featureinitiation code twice within a short period of time, e.g., pressing the“send” button twice within for example, approximately one-two seconds.Upon canceling the conference call the ongoing connection to the partyto be added, e.g., the third party, will be disconnected and theparty(ies) of the original call, e.g., the second party, will beretrieved. A detailed discussion of the signal flow for retrieving anoriginal call on hold before a conference call is established follows,using a three-way conference call as an example.

Assuming that the conference call has been initiated and the third partyis being alerted, in essence, the conference call setup procedure hasprogressed successfully in the normal manner to the point where theoriginal call to the second party is on hold (signals Call Held by LDS(CR=1) 5315, and Q.931 Call Proceeding 5316 already complete) and theparty to be added to the conference call is being alerted of an incomingcall (ISUP IAM 5317 already complete), if the MS 101 user enters afeature initiation code twice within a short period of time, e.g.,within a 1 to 2 seconds, e.g., presses the “send” button twice, the MS101 will send the VAP 103 two IS-136 Flash With Info 5502 and 5504messages sequentially. In response, VAP 103 send two IS-136 Flash withInfo ACK 5503 and 5505. messages sequentially to the MS 101.

When the VAP 103 gets the first IS-136 Flash with Info 5502 message fromthe mobile, the VAP 103 checks the call information record to determinesthat this is a three-way call, that the third party has not answered,that the original call with the second party is in a held state, andstarts the T37 timer, awaiting another IS-136 Flash with Info message,IS-136 Flash with Info 5504 message. If the timer T37 expires, the VAP103 will ignore the first Flash with Info message. Otherwise, the VAP103 gets the second IS-136 Flash with Info message, IS-136 Flash withInfo 5504 message from the MS 101, cancels the T37 timer, and sends anIS-136 Flash with Info Ack 5505 message to the MS 101. The VAP 103 alsodetermines that this is a request to disconnect the ongoing conferencecall connection and retrieve the original call. So the VAP 103 thensends a Q.931 Disconnect [CR=2] 5506 message to the LDS 104 and starts aT305 timer.

The VAP 103 sends a Q.931 Disconnect [CR=2] 5506 message to the LDS 104instructing it to disconnect the call setup to the party to be added,e.g., the third party. The LDS 104 then sends release messages, ISUP REL5507 message to PSTN DN2 125 b and Q.931 Release [CR=2] 5508 message tothe VAP 103, to terminate the call setup in mid-process. PSTN DN2 125 bresponds by releasing the call setup and sending a confirmation to theLDS 104, the ISUP RLC 5509 message. Once the VAP 103 gets a Q.931Release [CR=2] 5508 message from the LDS 104, it cancels the T305 timer,sends a Q.931 Release Complete[CR=2] 5510 message to the LDS 104followed by Q.932 Retrieve [CR=1] 5511 message to the LDS 104 and waitsfor Q.932 Retrieve Ack 5513 message from the LDS 104. However, if theT305 timer expires, the VAP 103 logs an error, releases CR=2 at its end,sends a Q.931 Release Complete 5510 message to the LDS 104 andcontinues.

When the call to the party to be added is released, the VAP 103 proceedsto retrieve the original call to the second party from hold andreconnect the call between the MS 101 user and the second party on thePSTN DN1 125 a. To do so, the VAP 103 sends the Q.932 Retrieve [CR=1]5511 message to the LDS 104 so that the LDS will retrieve the call onhold and starts the TRr timer. The LDS 104 responds to the VAP 103 witha Q.932 Retrieve Ack 5513 message and re-establishes the original callbetween the original parties to the conference call, e.g., the secondparty and the MS 101 user as illustrated by the dotted line with arrowslabeled 2-Way Call in Progress(CR=1) 5512. However, if the timer TRrexpires and the VAP 103 does not get Q.932 Retrieve Ack 5513 messagefrom the LDS 104, it will release all the resources. The VAP 103 willalso clear the call reference (CR=1) on its side and send a Q.931Release message to the LDS 104. Once the VAP 103 gets Q.931 Release ACKmessage from LDS 104, it will then send a WCS Release message to the NSP106 with a proper cause value (2^(nd) party could not be retrieved) andthe air interface usage for the call.

When the VAP 103 gets the Q.931 Retrieve Ack 5513 message from the LDS104, it sends a novel 3-Way Release [3rd Party not Answered] 5514message to the NSP 106. This novel WCS 3-Way Release message includesfields for MSID, Call Reference Number, and Cause (3rd Party notAnswered/3rd party dropped). When the NSP 106 receives 3-Way Release[3^(rd) party not answered] 5514 message from the VAP 103, it updates itcall record information in the WCSD to say that only 2-way call is nowin progress. If the NSP 106 receives a WCS Release message from the VAP103, the NSP 106 will update its call record to capture call usageinformation.

B. Deleting A Party From An Existing Call

The WCS provides the feature/function to allow an MS 101 user to delete(drop) a party from an active conference call. Once a conference callhas been established, an MS 101 user may enter delete a partyfeature/function code in the MS 101 which will trigger a party to bedropped from the conference call.

For ease of explanation and convenience, an exemplary embodiment isprovided below for a situation in which an MS 101 user drops the lastadded party from a three way conference call between an MS 101 user andtwo parties using PSTN telephones. However, one skilled in the art wouldrecognize that the present invention also similarly covers scenarioswhere the conference call includes more than three people and the MS 101user desires to delete (drop) a party other than the last added party.In such a case the delete a party feature/function message may alsoinclude, for example, a deactivation code and a directory numberindicating the party to be deleted.

Referring now to FIG. 56, a preferred embodiment is illustrated havingsignal flow for a situation when an MS 101 user drops the last addedparty from a three party conference call initiated by the MS 101 user,i.e., deleting (dropping) the third party during and active three-waycall. In this case, the MS user enters a delete last party message, forexample entering a conference call feature/function message by pressingthe “send” button twice, to thereby drop the last added call during athree-way call.

While a three-way call is in progress, 3-Way Call In-Progress (CR=1)5601, the MS 101 user decides to delete (drop) the last party added,PSTN DN2 125 b, from the active conference call. To achieve this, the MS101 user may, for example, enter the conference call feature/functionmessage by pressing the “send” button twice within a certain period oftime (e.g., a few seconds). This sequence will indicate to the VAP 103that the MS 101 user wishes to delete (drop) a party from a conferencecall, e.g., PSTN DN2 125 b.

In one example, the VAP 103 receives the first of two feature/functioninitiation codes, IS-136 Flash with Info 5602 message, from the MS 101.The VAP 103 checks the call information record to determine that athree-way active conference call is in progress. The VAP 103 starts aT37 timer awaiting another IS-136 Flash With Info message and sends anIS-136 Flash With Info Ack 5603 message back to the MS 101, indicatingreceipt of the earlier sent IS-136 Flash With Info 5602 message. If theVAP 103 gets another IS-136 Flash With Info message before the T37 timertimes out (e.g., within a few seconds), IS-136 Flash With Info 5604message from the MS 101, the VAP 103 determines that this is a requestto drop the last added party. In another embodiment the Flash With InfoMessage could be proceeded by the conference call feature functiondeactivation code and the DN to be dropped. This process would include aquery of the NSP 106 for instructions as to which line to drop. In anycase, if the timer T37 expires, the VAP will ignore the first Flash withInfo message.

Assuming the MS 101 has entered two Flash With Info messages before theT37 timer times out, the VAP 103 determines that a three-way call is inprogress and that this is a request to drop the last added party. Thus,the VAP 103 sends a Q.931 Info [CR=1, Drop] 5606 message to the LDS 104requesting it to disconnect, for example, the last added party of thethree-way call (CR=1).

The LDS 104 then initiates the Release process with PSTN DN2 125 b bysending an ISUP REL 5607 message to the PSTN DN2 125 b. After sending aQ.931 Info [CR=1, Drop] message to the LDS 104, the VAP 103 sends a3-Way Release [3rd party dropped] 5610 message with cause value as3^(rd) party dropped to the NSP 106. The LDS 104 may send back a Q.931Info [CR=1, Conf Display Info] 5609 message to the VAP 103 informing theVAP 103 that the last added call has been dropped. However, the VAP 103does not have to wait for the Q.931 Info [CR=1, Conf Display Info] 5609message and will ignore it when it gets this message if the VAP 103 hasalready sent the 3-Way Release [3rd party dropped] 5610 message. In anycase, the VAP 103 will send a 3-Way Release [3rd party dropped] 5610message to the NSP 106 and releases the last added party to theconference call. When the NSP 106 receives 3-Way Release message fromthe VAP 103, it will update the call record information to say that2-Way call is now in progress, 2-Way Call In Progress 5611, between PSTNDN1 125 a and MS 101.

In another embodiment the VAP 103 may play an announcement to one ormore party (ies) of the conference call indicating that a party is beingdropped from the active conference call.

Although particular embodiments of the present invention have been shownand described, it will be understood that it is not intended to limitthe invention to the preferred embodiments and it will be obvious tothose skilled in the art that various changes and modifications may bemade without departing from the spirit and scope of the presentinvention. Thus, the invention is intended to cover alternatives,modifications, and equivalents, which may be included within the spiritand scope of the invention as defined by the claims.

For example, while the IS-136 standard is used to illustrate theinvention in various embodiments described herein, the invention is notlimited to use in the IS-136 standard. The invention is also applicableto other cellular and/or PCS systems. Furthermore, while the accessmethodology employed by the various embodiments of the instant inventioninvolves the use of a Time Division Multiplexing Access (TDMA) scheme,the general concepts disclosed herein are not limited to the TDMA IS-136standard. The concepts are applicable to other access methodologies suchas, Frequency Division Multiple Access (FDMA), Code Division MultipleAccess (CDMA), or other multiple access techniques. As a result, the useof TDMA IS-136 standard is used to enable the invention and is in no wayintended to be a limitation of the invention.

The following applications are hereby incorporated by reference for allpurposes:

1. U.S. patent application Ser. No.09/223,316 by Chow et al. filed onDec. 30, 1998 entitled Neighborhood Cordless Service Call Handoff(Attorney Docket 3493.77826);

2. U.S. patent application Ser. No. 09/223,321 by Chow et al. filed onDec. 30, 1998 entitled Automatic Service Selection Feature forNeighborhood Cordless Service (Attorney Docket 3493.77824);

3. U.S. patent application Ser. No. 09/223,317 by Chow et al. filed onDec. 30, 1998 entitled Method and Apparatus for Billing a NeighborhoodCordless Service (Attorney Docket 3493.77825);

4. U.S. patent application Ser. No. 09/223,318 by Chow et al. filed onDec. 30, 1998 entitled Method and Apparatus for Over-the-Air Activationof Neighborhood Cordless Service (Attorney Docket 3493.77803);

5. U.S. patent application Ser. No. 09/223,322 by Chow et al. filed onDec. 30, 1998 entitled Method and Apparatus for Providing NeighborhoodResidential Cordless Service (Attorney Docket 3493.75951);

6. U.S. patent application Ser. No. 09/223,320 by Chow et al. filed onDec. 30, 1998 entitled Automatic Status Indicators For NeighborhoodCordless Service (Attorney Docket 3493.76142); and

7. U.S. patent application Ser. No. 09/224,724 by Chow et al. filed onDec. 31, 1998 entitled Instantaneous Conference Initiation (AttorneyDocket 3493.77827).

The following applications, which have each been filed on the same dayas the present application, are incorporated by reference as to theirentire contents for all purposes:

1. U.S. patent application Ser. No. 09/460,456, filed Dec. 13, 1999,(Attorney Docket No. 3493.79753; Client Reference No. 113421-CIP-13),entitled “Wireless Centrex Conference Call Adding A Party,” invented byChow et al.

2. U.S. patent application Ser. No. 09/460,385 filed Dec. 13, 1999,(Attorney Docket No. 3493.79754; Client Reference No. 113421-CIP-4),entitled “Wireless Centrex Conference Call Deleting A Party,” inventedby Chow et al.

3. U.S. patent application Ser. No. 09/460,116, filed Dec. 13, 1999,(Attorney Docket No. 3493.79752; Client Reference No. 113421-CIP-5),entitled “Wireless Centrex Automatic Callback,” invented by Chow et al.

4. U.S. patent application Ser. No. 09/458,831, filed Dec. 13, 1999,(Attorney Docket No. 3493.79755; Client Reference No. 113421-CIP-3),entitled “Unconditional Call Forwarding In A Wireless Centrex ServicesSystem,” invented by Chow et al.

5. U.S. patent application Ser. No. 09/458,842, filed Dec. 13, 1999,(Attorney Docket No. 3493.79756; Client Reference No. 113421-CIP-2),entitled “Programmable Ring-Call Forwarding In A Wireless CentrexServices System,” invented by Chow et al.

6. U.S. patent application Ser. No. 09/460,246, filed Dec. 13, 1999,(Attorney Docket No. 3493.79757; Client Reference No. 113421-CIP-1),entitled “Time-of-Day Call Forwarding In A Wireless Centrex ServicesSystem,” invented by Chow et al.

7. U.S. patent application Ser. No. 09/458,706, filed Dec. 13, 1999,(Attorney Docket No. 3493.79758; Client Reference No. 113421-CIP-6),entitled “Wireless Centrex Call Return,” invented by Chow et al.

8. U.S. patent application Ser. No. 09/459,470, filed Dec. 13, 1999,(Attorney Docket No. 3493.79759; Client Reference No. 113421-CIP-7),entitled “Wireless Centrex Call Transfer,” invented by Chow et al.

9. U.S. patent application Ser. No. 09/458,823, filed Dec. 13, 1999,(Attorney Docket No. 3493.79751; Client Reference No. 113421-CIP-14),entitled “Call Waiting In A Wireless Centrex System,” invented by Chowet al.

10. U.S. patent application Ser. No. 09/458,840, filed Dec. 13, 1999,(Attorney Docket No. 3493.79761; Client Reference No. 113421-CIP-8),entitled “Wireless Centrex Caller ID,” invented by Chow et al.

11. U.S. patent application Ser. No. 09/460,386, filed Dec. 13, 1999,(Attorney Docket No. 3493.79762; Client Reference No. 113421-CIP-9),entitled “Distinctive Ringing In A Wireless Centrex System,” invented byChow et al.

12. U.S. patent application Ser. No. 09/458,737, filed Dec. 13, 1999,(Attorney Docket No. 3493.79763; Client Reference No.113421-CIP-10),entitled “Speed Calling In A Wireless Centrex System,” invented by Chowet al.

13. U.S. patent application Ser. No. 09/459,541, filed Dec. 13, 1999,(Attorney Docket No. 3493.79764; Client Reference No. 113421-CIP-11),entitled “Busy Call Forwarding In A Wireless Centrex Services System,”invented by Chow et al.

14. U.S. patent application Ser. No. 09/460,151, filed Dec. 13, 1999,(Attorney Docket No. 3493.78954; Client Reference No. 113559-CIP),entitled “Wireless Centrex Call Hold,” invented by Chow et al.

15. U.S. patent application Ser. No. 09/460,392, filed Dec. 13, 1999,(Attorney Docket No. 3493.84270; Client Reference No. 113421-CIP-15),entitled “Wireless Centrex Feature Activation/Deactivation,” invented byChow et al.

16. U.S. patent application Ser. No. 09/460,391, filed Dec. 13, 1999,(Attorney Docket No. 3493.85229; Client Reference No. 113481-CIP),entitled “User Proactive Call Handling,” invented by Brachman et al.

17. U.S. patent application Ser. No. 09/459,324, filed Dec. 13, 1999,(Attorney Docket No. 3493.85230; Client Reference No. 113421-CIP),entitled “Wireless Centrex Services,” invented by Chow et al.

We claim:
 1. A method for blocking incoming calls to a mobile station ina wireless centrex system including an intelligent radio transceiverassigned to a called party, comprising the steps of: enabling said callblocking by entering a feature code with said mobile station; receivingsaid call blocking feature code at said intelligent radio transceiverfrom said mobile station registered in said wireless centrex system,said intelligent radio transceiver in communication with a local digitalswitch without being connected to any public cellular system;identifying a directory number from which incoming calls to said mobilestation will be blocked; verifying that said mobile station isauthorized to block incoming calls; and storing said director number ina database including a list of directory numbers from which incomingcalls to said mobile station will be blocked, via a line side interfaceto said local digital switch, said local digital switch in communicationwith a network server platform, said network server platform determiningwhere said mobile station is registered and how to route said incomingcalls to said mobile station.
 2. The method according to claim 1,wherein said step of identifying a directory number includes enteringthe digits of said directory number with said mobile station.
 3. Themethod according to claim 1, wherein said step of identifying adirectory number includes not entering said directory number with saidmobile station and entering only said feature code such that a directorynumber of said last active call is retrieved and used as said directorynumber for call blocking.
 4. The method according to claim 2, furthercomprising the step of blocking a call originating from said directorynumber which is intended for said mobile station.
 5. The methodaccording claim 4, further including the step of providing a particularcall treatment to said blocked call.
 6. The method according to claim 5,wherein said particular call treatment is determined based on a systemdefault.
 7. The method according to claim 5, wherein said particularcall treatment is dropping said blocked call without any announcement.8. The method according to claim 7, wherein a network server platforminstructs a local digital switch to disconnect said blocked call toaccomplish said dropping of said blocked call without any announcement.9. The method according to claim 8, wherein said local digital switchassumes processing of said blocked call and drops said call.
 10. Themethod according to claim 5, wherein said particular call treatment issending said call to a resource.
 11. The method according to claim 10,wherein said resource is selected from the group consisting of ananswering service, a voice mail system, and an operator assistant. 12.The method according to claim 11, wherein a network server platformdetermines which resource is selected and instructs a local digitalswitch to select said resource.
 13. The method according to claim 12,wherein said local digital switch and said resource process said blockedcall and drop said blocked call after processing of said blocked call bysaid resource is complete.
 14. The method according to claim 5, whereinsaid particular call treatment is providing said call with anannouncement.
 15. The method according to claim 14, wherein saidannouncement is selected from the group consisting of a system defaultcall screen message, a recorded message created by a user of said mobilestation, and a voice synthesized message defined by said user of saidmobile station.
 16. The method according to claim 15, further comprisinga step of selecting which of a plurality of intelligent transceiverswill play said announcement, and wherein a network server platformrequests one of said plurality of intelligent transceivers to play saidannouncement.
 17. The method according to claim 16, fturther comprisingthe step of playing said announcement to said blocked call callingparty.
 18. The method according to claim 5, wherein said blocked calloriginates from a telephone outside a wireless centrex system.
 19. Themethod according to claim 5, wherein said blocked call originates from atelephone within a wireless centrex system.
 20. A method for screeningincoming calls directed to a mobile station in a wireless centrex systemincluding an intelligent radio transceiver, comprising the steps of:enabling call screening by entering a feature code with said mobilestation; identifying a directory number from which incoming calls tosaid mobile station will be blocked; transmitting said feature code fromsaid mobile station through an intelligent radio transceiver to anetwork server platform, said intelligent radio transceiver incommunication with a local digital switch without being connected to anypublic cellular system, said local digital switch in communication withsaid network server platform, said network server platform determiningwhere said mobile station is registered and how to route incoming callsto said mobile station; verifying, with said network server platform,that said mobile station is authorized to block incoming calls; storing,with said network server platform, said directory number in a databaseincluding a list of directory numbers from which incoming calls to saidmobile station will be blocked; blocking said incoming call originatingfrom said directory number which is intended for said mobile station;providing a call treatment for said blocked incoming call; instructingsaid local digital switch with said network server platform via a lineside interface as how to dispose of said blocked incoming call accordingto said call treatment; and disconnecting said blocked incoming callusing said local digital switch.
 21. A system for allowing a calledparty to screen an incoming call to a mobile station in a wirelesscentrex system including an intelligent radio transceiver, comprising: alocal digital switch, responsive to an incoming call, creating a voicepath between an origin of the incoming call and the local digital switchvia a line side interface, said intelligent radio transceiver incommunication with said local digital switch without being connected toany public cellular system; a network server platform coupled to saidlocal digital switch r determining where the called mobile station isregistered and how to route said incoming call to said called mobilestation and fixer determining whether an incoming call is to be blocked;and said intelligent radio transceiver receiving a call screenactivate/deactivate instruction from said mobile station and instructingsaid network server platform to place calls originating from particulardirectory numbers in a call screen log.
 22. The system according toclaim 21, wherein said network server platform determines disposition ofsaid incoming call to be blocked.
 23. The system according to claim 22,wherein said network server platform comprises: a memory for storinginformation related to a profile of the mobile station; and acontroller, responsive to said local digital switch, for evaluating theprofile of a called party and instruction the local digital switch todetermine whether said incoming call is to be blocked and saiddisposition of said incoming call to be blocked.
 24. The systemaccording to claim 23, wherein said network server platform carries outa system default for said disposition according to the profile of thecalled party.
 25. The system according to claim 24, wherein said networkserver platform determines the disposition is to forward said incomingcall to a voice mail system.
 26. The system according to claim 24,further comprising: a voice processing unit for providing anannouncement to a calling party that the call has been screened, andwherein said network server platform determines the disposition is toprovide said announcement to the calling party.
 27. The system accordingto claim 24, wherein said network server platform determines thedisposition is to drop the call without an announcement.
 28. The systemaccording to claim 27, wherein said intelligent transceiver is a voiceaccess port in a wireless centrex system.